-
Notifications
You must be signed in to change notification settings - Fork 14.1k
std_detect: RISC-V: Best effort implication of target features by custom cfg
#145810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
a4lg
wants to merge
6
commits into
rust-lang:main
Choose a base branch
from
a4lg:std-detect-complex-implication
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
55a08bc
std_detect: Tidying for preparation of adding `@FEATURE` options
a4lg 09dc987
std_detect: Add implication from custom `cfg`
a4lg f4e9808
std_detect: RISC-V: Best effort implication by target config (group)
a4lg 61c6b10
std_detect: RISC-V: Best effort implication by target config (C-related)
a4lg 74851f7
std_detect: AArch64: Use `implied by cfg(...)`
a4lg 99d68f3
std_detect: Remove support for `implied by target_features`
a4lg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line seems redundant and could be folded into the macro itself: a feature is always implied by itself.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... unless
implied byis used (evenimplied by target_features:, which is to be removed in this PR suppresses self implication; see the macro expansion carefully).So,
zvkncruntime (std_detect) target feature is not directly implied byzvknccompiler target feature itself.Still, you are technically right since... for instance (in this place),
zvkncis just a collection of sub-extensions (zvkned,zvknhb...) andzvknccompiler target feature directly/indirectly enables all of them (indirectly enabling runtime target featurezvknc).The reason I keep
zvkncitself is to check validity of the compiler target feature (throughcheck_cfg_feature!).I think we can keep this (and similar lines) as-is (in this PR).