-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Make TLS accesses explicit in MIR #71192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -358,6 +358,13 @@ pub trait Machine<'mir, 'tcx>: Sized { | |
_mem: &Memory<'mir, 'tcx, Self>, | ||
_ptr: Pointer<Self::PointerTag>, | ||
) -> InterpResult<'tcx, u64>; | ||
|
||
fn thread_local_alloc_id( | ||
_ecx: &mut InterpCx<'mir, 'tcx, Self>, | ||
did: DefId, | ||
) -> InterpResult<'tcx, AllocId> { | ||
throw_unsup!(ThreadLocalStatic(did)) | ||
oli-obk marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I thought about errors in these default implementations again. Currently, we are inconsistent.
I am not sure what's better, but it seems odd not to be consistent here. |
||
} | ||
} | ||
|
||
// A lot of the flexibility above is just needed for `Miri`, but all "compile-time" machines | ||
|
Uh oh!
There was an error while loading. Please reload this page.