diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-04-25 06:46:49 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-25 06:46:49 +0200 |
| commit | 7e143e9043945006ad3338c9ff82e71a7de5e7c7 (patch) | |
| tree | 18afadf50c77ce6b0c2ef2bbfdc70a37bae09a39 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 5f33a8c026bb4f47cb184d066a809886b22fd172 (diff) | |
| parent | 047ed32148a39bc38ad18363ded9ab845dd313ee (diff) | |
| download | rust-7e143e9043945006ad3338c9ff82e71a7de5e7c7.tar.gz | |
Rollup merge of #110755 - TimNN:exp-tls, r=durin42
[LLVM17] Adapt to `ExplicitEmulatedTLS` removal.
https://github.com/llvm/llvm-project/commit/0d333bf0e3aa37e2e6ae211e3aa80631c3e01b85 removed the `ExplicitEmulatedTLS` field from `TargetOptions`.
Before that commit, `TargetMachine::useEmulatedTLS()` fell back to `TheTriple.hasDefaultEmulatedTLS()` if `ExplicitEmulatedTLS` was `false`/unset.
After that commit, `TargetMachine::useEmulatedTLS()` directly returns `Options.EmulatedTLS`, and the fallback to `TheTriple.hasDefaultEmulatedTLS()` was moved to `InitTargetOptionsFromCodeGenFlags`.
Since `rustc` does not use `InitTargetOptionsFromCodeGenFlags` (AFAICT) and instead manually builds `TargetOptions`, this PR initializes `EmulatedTLS` to `TheTriple.hasDefaultEmulatedTLS()`.
(I'm not really familiar with the details of what this option does, or if there are any tests that depend on `hasDefaultEmulatedTLS` being used correctly, so this PR is mostly untested (it does compile against LLVM17, though)).
`@rustbot` label: +llvm-main
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions