[SYCL][NATIVECPU] Fix TargetInfo initialization (DataLayoutString) #19711
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.
Some clang targets (for example for Arm) may not initialize
DataLayoutString
in their TargetInfo constructor, which meant callsgetDataLayoutString
right after the constructor cause an assert.This PR defers the initialization of the NativeCPU TargetInfo to after the call of
handleTargetFeatures
of the host cpu Target info, which on Arm initializesDataLayoutString
, but may also catch more initializations.