-
Notifications
You must be signed in to change notification settings - Fork 17
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
8279346: riscv: Unnecessary sign extension in BigInteger intrinsics #40
Conversation
👋 Welcome back yzhu! A progress list of the required criteria for merging this PR into |
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.
Looks good.
@yhzhu20 This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been no new commits pushed to the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@RealFYang) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
/sponsor |
Going to push as commit e73db5d. |
@RealFYang @yhzhu20 Pushed as commit e73db5d. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Reference: https://github.com/riscv-non-isa/riscv-elf-psabi-doc
" Scalars that are at most XLEN bits wide are passed in a single argument register, or on the stack by value if none is available.
When passed in registers or on the stack, integer scalars narrower than XLEN bits are widened according to the sign of their type up to 32 bits, then sign-extended to XLEN bits.
When passed in registers or on the stack, floating-point types narrower than XLEN bits are widened to XLEN bits, with the upper bits undefined."
So there is no need to do sign extension for signed integer input parameters.
Performed full jtreg tests with qemu without new failures.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/riscv-port pull/40/head:pull/40
$ git checkout pull/40
Update a local copy of the PR:
$ git checkout pull/40
$ git pull https://git.openjdk.java.net/riscv-port pull/40/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 40
View PR using the GUI difftool:
$ git pr show -t 40
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/riscv-port/pull/40.diff