diff options
| author | bors <bors@rust-lang.org> | 2017-06-24 04:42:18 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-06-24 04:42:18 +0000 |
| commit | 1ccc330d4b4741bbc0388fb55eb37b7b94f903d5 (patch) | |
| tree | aaade9b315e98c22d41c6772b4808fbf494ea365 /src/test/incremental/thinlto | |
| parent | 229d0d3266002d343cdd2f4a3bf7f2fe9da15f38 (diff) | |
| parent | 06540cb205545e5e7e509933af27142ca35eae17 (diff) | |
| download | rust-1ccc330d4b4741bbc0388fb55eb37b7b94f903d5.tar.gz rust-1ccc330d4b4741bbc0388fb55eb37b7b94f903d5.zip | |
Auto merge of #42687 - alexcrichton:windows-tls, r=sfackler
rustc: Enable #[thread_local] for Windows 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.
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions
