rust/library/panic_unwind/src/seh.rs, branch autohttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=auto2025-08-20T23:45:24+00:00Migrate `panic_unwind` to use `cfg_select!`2025-08-20T23:45:24+00:00Josh Stonejistone@redhat.com2025-08-20T23:45:24+00:00urn:sha1:d41cd486555e2f81b2dade5307316c40ba5c3f54Win: Use exceptions with empty data for SEH panic exception copies2025-07-08T20:07:42+00:00George Tokmajitokmajigeorge@gmail.com2025-07-08T19:19:38+00:00urn:sha1:96cdbb9ba77b9a840a1637e4dab05bb2cc64fef0
instead of a new panic
For unwinding with SEH, we currently construct a C++ exception with the
panic data. Being a regular C++ exception, it interacts with the C++
exception handling machinery and can be retrieved via
`std::current_exception`, which needs to copy the exception. We can't
support that, so we panic, which throws another exception, which the
C++ runtime tries to copy and store into the exception_ptr, which panics
again, which causes the C++ runtime to store a `bad_exception` instance.
However, this doesn't work because the panics thrown by the copy
function will be dropped without being rethrown, and causes unnecessary
log spam in stderr. Fix this by directly throwing an exception without
data, which doesn't cause log spam and can be dropped without being
rethrown.
intrinsics: use const generic to set atomic ordering2025-06-07T19:45:58+00:00Ralf Jungpost@ralfj.de2025-05-28T16:37:58+00:00urn:sha1:8808c9d34b04c8c9404aafaba2aeec4142963fa5library: Use size_of from the prelude instead of imported2025-03-07T04:20:38+00:00Thalia Archibaldthalia@archibald.dev2025-03-05T04:28:38+00:00urn:sha1:988eb1997014987caad878699ee1e7c000214508
Use `std::mem::{size_of, size_of_val, align_of, align_of_val}` from the
prelude instead of importing or qualifying them.
These functions were added to all preludes in Rust 1.80.
panic_unwind: Apply unsafe_op_in_unsafe_fn2025-02-14T15:36:17+00:00Eric Husseric@huss.org2025-02-13T20:44:32+00:00urn:sha1:331911e699f91bc890074fa42374c63dbea06c44Mark extern blocks as unsafe2025-02-09T17:11:13+00:00Michael Gouletmichael@errs.io2025-02-07T19:42:33+00:00urn:sha1:a4e7f8f9bf10588cb5519ae09a15be155499901fpanic_unwind: add `#![warn(unreachable_pub)]`2025-01-20T17:35:32+00:00Urgauurgau@numericable.fr2024-12-13T17:58:15+00:00urn:sha1:477ef65121a8c22371ff5df7f9b07795c3518283Remove allowing static_mut_refs lint2024-10-14T08:48:27+00:00mu001999mu001999@outlook.com2024-10-14T08:48:27+00:00urn:sha1:1e10e503fe7e9d645f1ba3638eb17d8ac306093bUse `&raw` in the standard library2024-09-26T00:03:20+00:00Josh Stonejistone@redhat.com2024-09-26T00:03:20+00:00urn:sha1:f4d9d1a0eaf7e5de8c368ac5af500adf9e06f6e7
Since the stabilization in #127679 has reached stage0, 1.82-beta, we can
start using `&raw` freely, and even the soft-deprecated `ptr::addr_of!`
and `ptr::addr_of_mut!` can stop allowing the unstable feature.
I intentionally did not change any documentation or tests, but the rest
of those macro uses are all now using `&raw const` or `&raw mut` in the
standard library.
Update tests for hidden references to mutable static2024-09-13T11:10:56+00:00Obei Sidegobei.sideg@gmail.com2024-08-24T03:49:09+00:00urn:sha1:3b0ce1bc33d30d7d116ee9af60df873e04bd74dc