erts: Fix spectre mitigation configure test #8006
Merged
Conversation
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
On Ubuntu 20.04 and later gcc adds -fcf-protection=full by default, which cannot be used together with -mbranch-protect. So we set -fcf-protection=none so that we can use -mbranch-protect.
garazdawi
added
team:VM
CT Test ResultsTests are running... https://github.com/erlang/otp/actions/runs/7458620478 Results for commit 13e1b29 To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts
// Erlang/OTP Github Action Bot |
jhogberg
approved these changes
Jan 9, 2024
garazdawi
deleted the
lukas/erts/fix-spectre-mitigation-configure-test
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On Ubuntu 20.04 and later gcc adds -fcf-protection=full by default, which cannot be used together with -mbranch-protect. So we set -fcf-protection=none so that we can use -mbranch-protect.