rust/tests/compile-fail/oom2.rs

// Validation forces more allocation; disable it.
// compile-flags: -Zmir-emit-validate=0
#![feature(box_syntax, custom_attribute, attr_literals)]
#![miri(memory_size=2048)]

fn main() {
    loop {
        ::std::mem::forget(box 42); //~ ERROR tried to allocate 4 more bytes
    }
}
Work on making validation test pass again Turns out that tracking write locks by their lifetime is not precise enough, but for now, we don't have an alternative. Also, we need to force_allocate what we acquire or else the memory will not be in the right state. 2017-08-07 17:40:18 -07:00			`// Validation forces more allocation; disable it.`
			`// compile-flags: -Zmir-emit-validate=0`
Optimize reads of field projections of ByValPairs. This helps in the case of field projections of the results of checked binary operations. E.g.: _1 = CheckedAdd(const 1i32, const 2i32); assert(!(_1.1: bool), "attempt to add with overflow" -> bb1 Previously, the `_1.1` field projection lvalue would force_allocate `_1` so it could read the memory in the old-style way. Now checked math with its assertions will not allocate at all. The oom2.rs compile-fail test had to be re-written, because the old version of it no longer allocates _at all_ (yay!), so it would hit the stack depth limit instead, from recursion. 2016-10-16 19:58:22 -06:00			`#![feature(box_syntax, custom_attribute, attr_literals)]`
test suite now also passes on MIR-libstd Also enable some tests that were disabled for no apparant reason. (The comment in zst.rs was wrong, the test was disabled also for miri execution.) Delete env_args test as the args can actually be queried with MIR-libstd (currently, they are always empty) 2017-05-26 20:27:39 -07:00			`#![miri(memory_size=2048)]`
test the memory limit 2016-07-05 13:04:53 +02:00
Optimize reads of field projections of ByValPairs. This helps in the case of field projections of the results of checked binary operations. E.g.: _1 = CheckedAdd(const 1i32, const 2i32); assert(!(_1.1: bool), "attempt to add with overflow" -> bb1 Previously, the `_1.1` field projection lvalue would force_allocate `_1` so it could read the memory in the old-style way. Now checked math with its assertions will not allocate at all. The oom2.rs compile-fail test had to be re-written, because the old version of it no longer allocates _at all_ (yay!), so it would hit the stack depth limit instead, from recursion. 2016-10-16 19:58:22 -06:00			`fn main() {`
			`loop {`
			`::std::mem::forget(box 42); //~ ERROR tried to allocate 4 more bytes`
test the memory limit 2016-07-05 13:04:53 +02:00			`}`
			`}`