about summary refs log tree commit diff
path: root/src/libstd/sys/windows/fast_thread_local.rs
AgeCommit message (Collapse)AuthorLines
2020-07-12rename fast_thread_local -> thread_local_dtor; thread_local -> thread_local_keyRalf Jung-4/+0
2019-12-21Require issue = "none" over issue = "0" in unstable attributesRoss MacArthur-1/+1
2019-05-15Revert "ensure fast thread local lookups occur once per access on macos"tyler-4/+0
This reverts commit d252f3b77f3b7d4cd59620588f9d026633c05816.
2019-05-15ensure fast thread local lookups occur once per access on macostyler-0/+4
2019-05-15remove dead code: requires_move_before_droptyler-4/+0
2019-02-28libstd => 2018Taiki Endo-1/+1
2018-12-25Remove licensesMark Rousskov-10/+0
2017-06-23rustc: Enable #[thread_local] for WindowsAlex Crichton-0/+18
I think LLVM has had support for quite some time now for this, we just never got around to testing it out and binding it. We've had some trouble landing this in the past I believe, but it's time to try again! This commit flags the `#[thread_local]` attribute as being available for Windows targets and adds an implementation of `register_dtor` in the `thread::local` module to ensure we can destroy these keys. The same functionality is implemented in clang via a function called `__tlregdtor` (presumably provided in some Windows runtime somewhere), but this function unfortunately does not take a data pointer (just a thunk) which means we can't easily call it. For now destructors are just run in the same way the Linux fallback is implemented, which is just keeping track via a single OS-based TLS key.