Ralf Jung 3c652032c0 be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

..

alias_through_mutation.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

aliasing_mut1.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

aliasing_mut2.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

aliasing_mut3.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

aliasing_mut4.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

box_exclusive_violation1.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

buggy_as_mut_slice.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

buggy_split_at_mut.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

deallocate_against_barrier.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

illegal_read1.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

illegal_read2.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

illegal_read3.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

illegal_read4.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

illegal_read5.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

illegal_write1.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

illegal_write2.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

illegal_write3.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

illegal_write4.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

illegal_write5.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

invalidate_against_barrier1.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

invalidate_against_barrier2.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

load_invalid_mut.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

load_invalid_shr.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

mut_exclusive_violation1.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

outdated_local.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

pass_invalid_mut.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

pass_invalid_shr.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

pointer_smuggling.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

return_invalid_mut_option.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

return_invalid_mut_tuple.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

return_invalid_mut.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

return_invalid_shr_option.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

return_invalid_shr_tuple.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

return_invalid_shr.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

shr_frozen_violation1.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

static_memory_modification.rs

the test suite assumes a libstd with full MIR; run test suite on xargo-built foreign libstds

2018-12-10 10:04:55 +01:00

transmute-is-no-escape.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00

unescaped_local.rs

be more clear which stack we are talking about

2019-02-12 10:51:03 +01:00