rust/tests/ui/intrinsics, branch auto

Mark float intrinsics with no preconditions as safe

2025-09-22T00:37:51+00:00

disable core dumps for panic-uninitialized-zeroed

2025-09-08T14:41:17+00:00

That test causes a large amount of crashes. If a system has a /proc/sys/kernel/core_pattern that uploads core dumps enabled, it will take a long time to complete. Set dumpable to 0 to avoid that. Before: $ time ./panic-uninitialized-zeroed real 0m47.457s user 0m0.023s sys 0m0.021s After: $ ./panic-uninitialized-zeroed real 0m0.029s user 0m0.019s sys 0m0.010s

Auto merge of #145358 - Kobzol:symbol-name-sort, r=nnethercote

2025-08-22T07:13:07+00:00

Sort mono items by symbol name Trying to claw back cycles/branch/cache miss losses from https://github.com/rust-lang/rust/pull/144722.

Sort mono items by symbol name

2025-08-15T12:04:32+00:00

Rollup merge of #144631 - fneddy:fix_be_test_intrinsic_const_bad, r=compiler-errors

2025-08-14T19:48:42+00:00

Fix test intrinsic-raw_eq-const-bad for big-endian The test fails on s390x and presumably other big-endian systems, due to print of raw values. To fix the tests remove the raw output values in the error note with normalize-stderr.

Fix parallel rustc not being reproducible due to unstable sorting of items.

2025-08-13T00:59:32+00:00

Rollup merge of #144192 - RalfJung:atomicrmw-ptr, r=nikic

2025-08-08T19:22:44+00:00

atomicrmw on pointers: move integer-pointer cast hacks into backend Conceptually, we want to have atomic operations on pointers of the form `fn atomic_add(ptr: *mut T, offset: usize, ...)`. However, LLVM does not directly support such operations (https://github.com/llvm/llvm-project/issues/120837), so we have to cast the `offset` to a pointer somewhere. This PR moves that hack into the LLVM backend, so that the standard library, intrinsic, and Miri all work with the conceptual operation we actually want. Hopefully, one day LLVM will gain a way to represent these operations without integer-pointer casts, and then the hack will disappear entirely. Cc ```@nikic``` -- this is the best we can do right now, right? Fixes https://github.com/rust-lang/rust/issues/134617

Print thread ID in panic message if thread name is unknown

2025-08-06T23:59:47+00:00

`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 '' panicked at src/main.rs:3:5: explicit panic To something like this: thread '' (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.

Fix tests for big-endian

2025-07-30T11:53:04+00:00

The tests fail on s390x and presumably other big-endian systems, due to print of raw values and padding bytes. To fix the tests remove the raw output values in the error note with `normalize-stderr`.

Add `ignore-backends` annotations in failing GCC backend ui tests

2025-07-23T11:48:04+00:00