RISC-V: refine fpu reg context offset #1257
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
The index 0 and 1 are general register which should depends on _XLEN_. Signed-off-by: wangfei_chen <[email protected]>
Member
|
There are the following 4 possible configurations and the corressponding offsets: The correct formula to calculate the offset should be |
Signed-off-by: Gaurav Aggarwal <[email protected]>
|
aggarg
approved these changes
Mar 13, 2025
aggarg
approved these changes
Mar 13, 2025
tony-josi-aws
approved these changes
Mar 13, 2025
Contributor
Author
|
It looks good to me, thanks for refine. |
kstribrnAmzn
approved these changes
Mar 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
The index 0 and 1 are stored for general register which should depends on XLEN.
Description
Test Steps
Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.