Skip to content
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

-mfloat-abi=hard should be a default flag for the armv7a-none-eabihf target #1193

Closed
chrisnc opened this issue Aug 26, 2024 · 1 comment · Fixed by #1194
Closed

-mfloat-abi=hard should be a default flag for the armv7a-none-eabihf target #1193

chrisnc opened this issue Aug 26, 2024 · 1 comment · Fixed by #1194

Comments

@chrisnc
Copy link
Contributor

chrisnc commented Aug 26, 2024

The arm*v7r-none-eabihf and thumb*-none-eabihf targets both add -mfloat-abi=hard to the default compiler flags, but armv7a-none-eabihf does not. This results in needing to specify it manually for C libraries when using this target.

In GCC 10, -march=arvm7-a by itself implied hardware floating-point support and the hardfloat ABI, but in 11 and later these need to be explicit for none OS targets. cc-rs already provides -mfpu=vfpv3-d16 to handle one part of this, but doesn't change the ABI. -linux- targets still have the behavior of -march=armv7-a implying the hf ABI, so only -none-eabihf needs to be changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
@chrisnc and others