8290496: riscv: Fix build warnings-as-errors with GCC 11

[RealFYang]

Like AArch64 port, RISC-V port defines DEOPTIMIZE_WHEN_PATCHING and does not make use of C1 runtime patching.
Then there is no need to implement class NativeMovRegMem in the port-specific code. But that will make GCC 11 unhappy.

One way would be guarding the C1 shared code like class PatchingStub which uses class NativeMovRegMem under condition #ifndef DEOPTIMIZE_WHEN_PATCHING. But turns out class PatchingStub are still partially used (mainly the PatchID enum) even under DEOPTIMIZE_WHEN_PATCHING.

So PR takes another way fixing this warning by implementing the NativeMovRegMem class for RISC-V like Like AArch64 port.

Testing: release & fastdebug build OK without --disable-warnings-as-errors

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8290496: riscv: Fix build warnings-as-errors with GCC 11

Reviewers

• Yadong Wang (@yadongw - Author)
• Feilong Jiang (@feilongjiang - Author)
• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9550/head:pull/9550
$ git checkout pull/9550

Update a local copy of the PR:
$ git checkout pull/9550
$ git pull https://git.openjdk.org/jdk pull/9550/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 9550

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9550.diff

[bridgekeeper]

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

[openjdk]

@RealFYang The following label will be automatically applied to this pull request:

• hotspot-compiler

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (da4b3709)

[yadongw]

lgtm

[yadongw]

Try GCC 12 if possible?

[feilongjiang]

Try GCC 12 if possible?

I have tried the native release build with GCC 12 (on Ubuntu 22.04, gcc version 12.0.1 20220319 (experimental)). The warning did not appear after this patch.

[RealFYang]

@yadongw @feilongjiang : Thanks. Could we have a Reviewer please? @shipilev ?

[shipilev]

Looks okay!

[openjdk]

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

8290496: riscv: Fix build warnings-as-errors with GCC 11

Reviewed-by: yadongwang, fjiang, shade

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 32 new commits pushed to the master branch:

• a3e07d9: Merge
• e062dff: 8290524: Typo in javadoc of MemorySegment/MemoryAddress
• a6bab2a: 8288482: JFR: Cannot resolve method
• 4dc421c: 8290417: CDS cannot archive lamda proxy with useImplMethodHandle
• 2ea3f54: 8290495: Micro-optimize Method::can_be_statically_bound assertions
• 9714791: 8190907: Windows 10 default Korean Font Malgun Gothic available not used by GUI elements even though available without Korean Language Pack
• 4358864: 8290511: compiler/vectorapi/TestMaskedMacroLogicVector.java fails IR verification
• 7b418f9: 8287916: Address the inconsistency between the constant array and pool size
• 41ef2b2: 8285407: Improve Xalan supports
• d991ec4: 8282676: Improve subject handling
• ... and 22 more: https://git.openjdk.org/jdk/compare/af86cd3d8c0f8a874d1b738ad0caeeb7cd4c61d0...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[RealFYang]

Looks okay!

Thanks all for the review.

/integrate

[openjdk]

Going to push as commit 5425573.
Since your change was applied there have been 32 commits pushed to the master branch:

• a3e07d9: Merge
• e062dff: 8290524: Typo in javadoc of MemorySegment/MemoryAddress
• a6bab2a: 8288482: JFR: Cannot resolve method
• 4dc421c: 8290417: CDS cannot archive lamda proxy with useImplMethodHandle
• 2ea3f54: 8290495: Micro-optimize Method::can_be_statically_bound assertions
• 9714791: 8190907: Windows 10 default Korean Font Malgun Gothic available not used by GUI elements even though available without Korean Language Pack
• 4358864: 8290511: compiler/vectorapi/TestMaskedMacroLogicVector.java fails IR verification
• 7b418f9: 8287916: Address the inconsistency between the constant array and pool size
• 41ef2b2: 8285407: Improve Xalan supports
• d991ec4: 8282676: Improve subject handling
• ... and 22 more: https://git.openjdk.org/jdk/compare/af86cd3d8c0f8a874d1b738ad0caeeb7cd4c61d0...master

Your commit was automatically rebased without conflicts.

[openjdk]

@RealFYang Pushed as commit 5425573.

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