Sync with spike version of softfloat #26
Open
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
troibe
force-pushed
the
sync-with-spike-version-3d
branch
2 times, most recently
from
390fa46 to
8c8f25e
Compare
troibe
force-pushed
the
sync-with-spike-version-3d
branch
from
8c8f25e to
6ffd8a8
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.
Addresses #24
It adds the following modifications of softfloat version 3d from Spike:
As far as I can tell all of these were added for the RISC-V vector extension.
Any modifications related to the build system in Spike were left out.
As I'm just a user and by no means a softfloat expert, I would appreciate some advice on these things before merging:
specialization.hwere specific to RISC-V. What would be the quickest way of optaining the special values for ARM and 8086? Then I'll adjust them from the RISC-V vaues which I currently just copied.