8308408: Build failure with -Werror=maybe-uninitialized in libjli/java.c with GCC8

[DamonFool]

May I get review for this change which fixes the build broken with GCC8?
Thanks.

---

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-8308408: Build failure with -Werror=maybe-uninitialized in libjli/java.c with GCC8

Reviewers

• Alan Bateman (@AlanBateman - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 14057

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

• core-libs

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 (2b4ac63c)

[AlanBateman]

This looks okay

[openjdk]

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

8308408: Build failure with -Werror=maybe-uninitialized in libjli/java.c with GCC8

Reviewed-by: alanb

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 master 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.

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

[DamonFool]

This looks okay

Thanks @AlanBateman for your quick review.

May I push it now since it's a build breakage?
Thanks.

[AlanBateman]

May I push it now since it's a build breakage? Thanks.

Yes, the change is trivial so please go ahead.

[DamonFool]

May I push it now since it's a build breakage? Thanks.

Yes, the change is trivial so please go ahead.

Thanks @AlanBateman .
/integrate

[openjdk]

Going to push as commit 690d396.

[openjdk]

@DamonFool Pushed as commit 690d396.

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