-
-
Notifications
You must be signed in to change notification settings - Fork 15k
Stable MIR's thread local not properly handled on unwind #112940
Copy link
Copy link
Closed
Labels
E-mediumCall for participation: Medium difficulty. Experience needed to fix: Intermediate.Call for participation: Medium difficulty. Experience needed to fix: Intermediate.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Metadata
Metadata
Assignees
Labels
E-mediumCall for participation: Medium difficulty. Experience needed to fix: Intermediate.Call for participation: Medium difficulty. Experience needed to fix: Intermediate.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
rust/compiler/rustc_smir/src/stable_mir/mod.rs
Lines 113 to 114 in 7f74ae5
TLVis left set to a dangling pointer iffunwinds. This is unsound because a later call towithwill use that dangling pointer. There is a similar issue withwithand unwinding.since you're on the Stable MIR cc list:
cc @oli-obk, @celinval