rust/tests/ui/numbers-arithmetic/overflowing-pow-unsigned.rs

//@ run-fail
//@ regex-error-pattern: thread 'main'.*panicked
//@ error-pattern: attempt to multiply with overflow
//@ needs-subprocess
//@ compile-flags: -C debug-assertions

fn main() {
    let _x = 2u32.pow(1024);
}
Move tests from `test/run-fail` to UI 2020-04-16 15:50:32 +09:00			`//@ run-fail`
Print thread ID in panic message if thread name is unknown `panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print. 2023-09-11 00:59:31 -04:00			`//@ regex-error-pattern: thread 'main'.*panicked`
			`//@ error-pattern: attempt to multiply with overflow`
tests: use `needs-subprocess` instead of `ignore-{wasm32,emscripten,sgx}` 2025-01-23 16:36:54 +08:00			`//@ needs-subprocess`
Add test for overflowing pow This would catch regressions of issue #28012. 2015-09-13 22:19:36 -04:00			`//@ compile-flags: -C debug-assertions`

			`fn main() {`
Fix overflow checking in unsigned pow() The pow() method for unsigned integers produced 0 instead of trapping overflow for certain inputs. Calls such as 2u32.pow(1024) produced 0 when they should trap an overflow. This also adds tests for the correctly handling overflow in unsigned pow(). For issue number #34913 2016-07-20 18:23:52 -04:00			`let _x = 2u32.pow(1024);`
Add test for overflowing pow This would catch regressions of issue #28012. 2015-09-13 22:19:36 -04:00			`}`