[LLVM17] Adapt to ExplicitEmulatedTLS
removal.
#110755
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
llvm/llvm-project@0d333bf removed the
ExplicitEmulatedTLS
field fromTargetOptions
.Before that commit,
TargetMachine::useEmulatedTLS()
fell back toTheTriple.hasDefaultEmulatedTLS()
ifExplicitEmulatedTLS
wasfalse
/unset.After that commit,
TargetMachine::useEmulatedTLS()
directly returnsOptions.EmulatedTLS
, and the fallback toTheTriple.hasDefaultEmulatedTLS()
was moved toInitTargetOptionsFromCodeGenFlags
.Since
rustc
does not useInitTargetOptionsFromCodeGenFlags
(AFAICT) and instead manually buildsTargetOptions
, this PR initializesEmulatedTLS
toTheTriple.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