Generated STM32 targets with FPU #255
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
…has the 'FPU' interrupt. Also make the register definition path public so a user can use the defs to create a custom target if they need.
mattnite
force-pushed
the
stm32_fpu_targets
branch
from
3446298
to
1b791b3
Compare
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.
This PR adds some logic to use the floating point version of a target if the core has an interrupt labeled "FPU". It also adds a target with the FPU features set and hard float abi for the M33 and M7 cores, and for the non-f M7 it sets the soft float abi.
Also makes the register defs path public in chips.zig so a user can specify their own target but still use the generated registers if they need to for whatever reason.
Addresses #245 (comment)