8373255: Unexpected iobj and ipdb files after JDK-8370438

[erikj79]

When using -LTCG with Visual Studio, then by default, the linker will output an extra .iobj file in the same directory as the target file. In the OpenJDK build that means this file, along with the accompanying .ipdb file, will end up in the JDK image. To fix this, we need to apply a similar fix to JDK-8372643 and add an extra parameter that defines the location of this file.

---

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-8373255: Unexpected iobj and ipdb files after JDK-8370438 (Bug - P4)

Reviewers

• Sergey Bylokhov (@mrserb - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28709

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8373255: Unexpected iobj and ipdb files after JDK-8370438

Reviewed-by: serb

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

• c9ab330: 8373116: Genshen: arraycopy_work should be always done for arrays in old gen during young concurrent marking
• 3ea82b9: 8373272: Genshen: ShenandoahOldGenerationTest fails after JDK-8373056
• b1c9550: 8372554: Test windows-x64-cmp-baseline failed due to differences with splashscreen object file
• ... and 2 more: https://git.openjdk.org/jdk/compare/8df3f3d3417bc8fdb5a75d986e084441bbf6ebd2...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.

[openjdk]

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

• build

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 (0c217dad)

[mrserb]

Is it possible that this issue is similar to #28712 ?

[mrserb]

I confirm that it fixes the issue.

[mrserb]

Is it possible that this issue is similar to #28712 ?

Seems so. Could you please confirm this with the full test set in mach5? It is not necessary to revert "that revert" until #28676 is fixed, but it would be good to know that the issue on windows is resolved.

[dholmes-ora]

Yes it does appear that this is what is breaking the cmp-baselines build on Windows.

[erikj79]

This should indeed fix the cmp-baseline build on Windows. I had missed that issue, sorry about that. I'm running a full builds tier1-5 on this branch (where the revert has not happened) to confirm.

[erikj79]

Confirmed that this fixes the cmp-baseline issue as well, so you can re-enable LTO for splashscreen if you wish.

[erikj79]

/integrate

[openjdk]

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

• 8c8d21d: 8373295: Wrong log tag for UseCompressedOops ergo setting
• a4eb57c: 8367028: compiler/c2/irTests/TestFloat16ScalarOperations.java failing intermittently because of constant folding
• 830c4d3: 8366272: The os::xxx APIs do not manage errno correctly
• ... and 14 more: https://git.openjdk.org/jdk/compare/8df3f3d3417bc8fdb5a75d986e084441bbf6ebd2...master

Your commit was automatically rebased without conflicts.

[openjdk]

@erikj79 Pushed as commit 831fe94.

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

[erikj79]

/backport :jdk26

[openjdk]

@erikj79 the backport was successfully created on the branch backport-erikj79-831fe94c-jdk26 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk26, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit 831fe94c from the openjdk/jdk repository.

The commit being backported was authored by Erik Joelsson on 9 Dec 2025 and was reviewed by Sergey Bylokhov.

Thanks!

If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-erikj79-831fe94c-jdk26:backport-erikj79-831fe94c-jdk26
$ git checkout backport-erikj79-831fe94c-jdk26
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-erikj79-831fe94c-jdk26