-
Notifications
You must be signed in to change notification settings - Fork 201
Correct the default Bazel vector instructions options #782
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
6c8ccca
Correct the default Bazel vector instructions options
mhucka 40c0bf2
Correct the default Bazel vector instructions options
mhucka 0ce15cf
Update documentation about using bazel
mhucka 84ae512
Merge branch 'master' into mh-more-bazel-changes
mhucka d2aa967
Use = in option args more consistently
mhucka ca494ef
Remove build_filters from bazel test invocation
mhucka 3852481
Remove unnecessary second bazel build of apps
mhucka c684a08
Merge branch 'master' into mh-more-bazel-changes
mhucka 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 runs into the same problem as in #710 - the shell has the
-eoption so the script will exit here if any ofavx2orssefeatures were missing. To have a positive condition, you need to rewrite this asThere 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.
So, I tested the following, and it does not exit early. Do you have an environment where it doesn't work this way?
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.
I stand corrected - per bash set -e doc for the
&&and||lists it is only the last command that counts forerrexit. I got confused, because on my Debian box it indeed exits early in an interactive session. This happens because interactive bash runs some fancy prompt functions which try to restore the exit status of the last command and that triggerserrexit.With your snippet (and the same system bashrc) this can be reproduced with
TLDR - it is OK as is.
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.
Wow, that's unobvious. Thanks for the info!