Fix no_std detection for target triples #69563
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.
The current check for wether a target is no_std or not is matching for the string
-none-
in a target triple. This doesn't work for triples that end in-none
, likeaarch64-unknown-none
.Fix this by matching for
-none
instead.I checked for all the current target triples containing
none
, and this should not generate any false positives.This fixes an issue encountered in #68334