-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add Target support for architectures with implementation specific vector size. #6786
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
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 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 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
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.
(1) There is lots of code that assumes that Target::to_string() is roundtribble with the Target ctor, so this really needs to emit this as
-vector_bits_%d
to match the parser(2) to_string() is expected to emit a 'canonical' version of the Target string, so order matters. Currently, we emit all features in alphabetical order (because std::map). Since this is parsed as though it were a feature, IMHO it should be emitted as a feature (and thus sorted with the v's). I guess we could declare it to always come last, but it will be a little weird.
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.
The colon is left over from a previous syntax. I thought I had test coverage for that.
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.
Fixed the formatting and added test coverage.
The idea here is that this is not a feature flag because it doesn't show up in the feature flags set. I feel like any code dealing with it needs to know that it can have an arbitrary number inside it anyway, so the fact that it canonicalizes to the end is fine, and perhaps a good signal that it is a bit different.
One issue is this doesn't play well with the can_use_target features machinery. We'll have to extend that anyway to handle an arbitrary numeric parameter. (And I really don't want to allocate a large number of feature flags to represent all the likely sizes.)