Set mcpu instead of mfpu in aarch64 #208
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
According to documentation:
https://developer.arm.com/documentation/dui0774/l/Compiler-Command-line-Options/-mfpu
https://stackoverflow.com/questions/72319839/aarch64-gcc-equivalent-option-for-mfpu-neon
-mfpuis already set in aarch64 environments (with neon applied) and while GCC might ignore the option, clang outright errors and refuses to build. When using WSL chroot to build with both GCC and clang,-mcpu=nativefalls back to a generic aarch64 processor. When building on known processors likecortex-a57, (i.e. on a RPi itself) the switch should properly adapt.Allows successful building for aarch64.