-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[RISC-V] Use common CodeGen::genHomeRegisterParams #101288
Merged
Merged
Changes from 10 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
25ab569
Code review from #101114
tomeksowi 6c01d95
Use common genHomeRegisterParams on RISC-V
tomeksowi 5423299
Make passSlot integer-only because we know hardware floating-point ca…
tomeksowi 06e9d65
Repurpose genHomeSwiftStructParameters for reassembling structs on RI…
tomeksowi 85c2217
Code review
tomeksowi 2a97285
Merge branch 'main' into use-new-abi-classifiers
tomeksowi 5a0aede
genHome(Reassembled=>Stack)Parameters rename
tomeksowi 4806478
Call genHomeStackParams(true) in prolog generation for RISC-V to avoi…
tomeksowi 123fcee
Leave Swift codes alone
tomeksowi 9c565ac
Make a RISC-V specific routine for homing stack parts of split parame…
tomeksowi c86cb09
Move genHomeStackPartOfSplitParameter out of genHomeSwiftStructParame…
tomeksowi 7989c18
Merge branch 'main' into use-new-abi-classifiers
tomeksowi 5225a43
fix x64 build
tomeksowi f7b0bcc
format
tomeksowi bfaf9ce
review
tomeksowi 2d2717e
remove comment
tomeksowi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you move this handling outside
genHomeRegisterParams
, before it is called? Prolog generation becomes much more constrained aftergenHomeRegisterParams
has run, and this handling doesn't have anything to do with moving registers to their initial locations. I would also switch to useinitReg
instead ofREG_SCRATCH
for the same reason (usingREG_SCRATCH
wouldn't work on other platforms at the point this runs, for example. I guess it works because RISCV64 never allocatesREG_SCRATCH
for anything, but on other platforms that's not a valid register to clobber aftergenHomeRegisterParams
.).You can factor the code in the stack case from
genHomeSwiftStructParameters
to avoid duplicating that logic.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My thinking was split parameter homing can happen can only if there are some argument registers to home (otherwise the parameter wouldn't be split), but ok, it can also be outside.