8263504: Some OutputMachOpcodes fields are uninitialized

[shipilev]

SonarCloud reports:
2 uninitialized fields at the end of the constructor calls

class OutputMachOpcodes : public OutputMap {
  int begin_inst_chain_rule;
  int end_inst_chain_rule;
  int begin_rematerialize; // <--- this
  int end_rematerialize;   // <--- and this
  int end_instructions;
public:
  OutputMachOpcodes(FILE *hpp, FILE *cpp, FormDict &globals, ArchDesc &AD)
    : OutputMap(hpp, cpp, globals, AD, "MachOpcodes"),
      begin_inst_chain_rule(-1), end_inst_chain_rule(-1), end_instructions(-1)

They are written on all paths that I can see, but they should be initialized anyway, at least for proper checks in closing().

---

Progress

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

Issue

• JDK-8263504: Some OutputMachOpcodes fields are uninitialized

Reviewers

• Vladimir Kozlov (@vnkozlov - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk pull/2967/head:pull/2967
$ git checkout pull/2967

[bridgekeeper]

👋 Welcome back shade! 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]

@shipilev 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 (fda6780)

[vnkozlov]

Good and trivial.

[openjdk]

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

8263504: Some OutputMachOpcodes fields are uninitialized

Reviewed-by: kvn

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

• a6e056f: 8263125: During deoptimization vectors should reassign scalarized payload after all objects are reallocated.
• 65421fa: 8213177: GlobalCounter::CSContext could be an enum class

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

[shipilev]

/integrate

[openjdk]

@shipilev Since your change was applied there have been 22 commits pushed to the master branch:

• f7e0a09: 8263425: AArch64: two potential bugs in C1 LIRGenerator::generate_address()
• 554dd29: 8263564: Consolidate POSIX code for runtime exit support: os::shutdown, os::abort and os::die
• da9ead5: 8263399: CDS should archive only classes allowed by module system
• 9c84899: 8263555: use driver-mode to run ClassFileInstaller
• 8e562d2: 8263477: serviceability/sa/ClhsdbDumpheap.java timed out
• a7aba2b: 8263549: 8263412 can cause jtreg testlibrary split
• d339320: 8263136: C4530 was reported from VS 2019 at access bridge
• a528771: 8262491: AArch64: CPU description should contain compatible board list
• 86e4c75: 8256156: JFR: Allow 'jfr' tool to show metadata without a recording
• 0b68ced: 8263548: runtime/cds/appcds/SharedRegionAlignmentTest.java fails to compile after JDK-8263412
• ... and 12 more: https://git.openjdk.java.net/jdk/compare/a9b156d358b0436584a33f71abc00c9bed9d47a3...master

Your commit was automatically rebased without conflicts.

Pushed as commit b371f90.

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