8278531: riscv: Remove duplicate code bitset_to_fregs

[feilongjiang]

After JDK-8278337, the definition of bitset_to_fregs is just same as bitset_to_regs.

Hotspot and jdk tier1 passed on the unmatched board. All tests were tested without new failures.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8278531: riscv: Remove duplicate code bitset_to_fregs

Reviewers

• Fei Yang (@RealFYang - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/riscv-port pull/28/head:pull/28
$ git checkout pull/28

Update a local copy of the PR:
$ git checkout pull/28
$ git pull https://git.openjdk.java.net/riscv-port pull/28/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28

View PR using the GUI difftool:
$ git pr show -t 28

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/riscv-port/pull/28.diff

[bridgekeeper]

👋 Welcome back fjiang! A progress list of the required criteria for merging this PR into riscv-port will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 00: Full (ab494edf)

[RealFYang]

Looks good.

[openjdk]

@feilongjiang 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:

8278531: riscv: Remove duplicate code bitset_to_fregs

Reviewed-by: fyang

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 riscv-port branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

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 in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[feilongjiang]

/integrate

[openjdk]

@feilongjiang
Your change (at version ab494ed) is now ready to be sponsored by a Committer.

[RealFYang]

/sponsor

[openjdk]

Going to push as commit e7d712c.
Since your change was applied there have been 46 commits pushed to the riscv-port branch:

• f29745d: Merge branch 'master' into riscv-port
• 066b348: 8277807: Increase default initial concurrent refinement threshold
• ec0a5ac: Merge
• d40e90b: 8278521: ProblemList java/lang/management/ThreadMXBean/ThreadLists.java
• 918b350: 8278516: Typos in snippet for java.compiler
• fcd67a5: 8278185: Custom JRE cannot find non-ASCII named module inside
• abebde7: 8278421: G1: Remove unused HeapRegion::verify
• bc31ccc: 8278312: Update SimpleSSLContext keystore to use SANs for localhost IP addresses
• 01b30bf: 8253860: PPC: Relocation::pd_set_data_value conflates compressed oops and klasses
• 09831e7: 8273146: Start of release updates for JDK 19
• ... and 36 more: https://git.openjdk.java.net/riscv-port/compare/9d030632a1359b20ac71cad7b228b76bbff29f1d...riscv-port

Your commit was automatically rebased without conflicts.

[openjdk]

@RealFYang @feilongjiang Pushed as commit e7d712c.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.