diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-06-03 21:53:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-03 21:53:36 +0200 |
| commit | d096ebf8d93e78b429c5c5866ecc60b3a5d9ed18 (patch) | |
| tree | aebd489ff5f107259759c39157951aeb37b72d77 /compiler/rustc_monomorphize/src | |
| parent | 27a894f86f361adee3ff5b25d685bb117c623461 (diff) | |
| parent | 8bf515330fb68ba10a54e9087a2b5629a968e766 (diff) | |
| download | rust-d096ebf8d93e78b429c5c5866ecc60b3a5d9ed18.tar.gz rust-d096ebf8d93e78b429c5c5866ecc60b3a5d9ed18.zip | |
Rollup merge of #141455 - joboet:tls_exhaustion_abort, r=tgross35
std: abort the process on failure to allocate a TLS key The panic machinery uses TLS, so panicking if no TLS keys are left can lead to infinite recursion (see https://github.com/rust-lang/rust/issues/140798#issuecomment-2872307377). Rather than having separate logic for the panic count and the thread name, just always abort the process if a TLS key allocation fails. This also has the benefit of aligning the key-based TLS implementation with the documentation, which does not mention that a panic could also occur because of resource exhaustion.
Diffstat (limited to 'compiler/rustc_monomorphize/src')
0 files changed, 0 insertions, 0 deletions