8371967: Add Visual Studio 2026 to build toolchain for Windows

[YaSuenag]

Microsoft has been published Visual Studio 2026, and it can build OpenJDK for Windows without any code changes if we add it to build toolchain.

Now we should support new Visual Studio for maintainability.

---

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-8371967: Add Visual Studio 2026 to build toolchain for Windows (Bug - P4)

Reviewers

• Erik Joelsson (@erikj79 - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28342

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8371967: Add Visual Studio 2026 to build toolchain for Windows

Reviewed-by: erikj

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

• 9ec773a: 8371689: (fs) CopyMoveHelper.copyToForeignTarget use of sourcePosixView is confusing
• 52ffe8a: 8371156: PBKDF2 default values should not be DER encoded
• 6385c66: 8371607: Remove GCSharedStringsDuringDumpWb.java after JDK-8362561
• ... and 14 more: https://git.openjdk.org/jdk/compare/7d35a283cf2497565d230e3d5426f563f7e5870d...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]

@YaSuenag 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 (89440bb6)

[erikj79]

Looks good to me, as long as it works. I don't have the ability to verify myself so will have to take your word for it.

[YaSuenag]

Thanks @erikj79 for your review!
I tested this change with VS 2026 Community Edition on WSL1 (Fedora 42) on Windows 11 25H2.

[YaSuenag]

/integrate

[openjdk]

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

• 2e68b79: 8364991: Incorrect not-exhaustive error
• 36b66e1: 8371778: Make MallocMemorySummary::_snapshot a DeferredStatic
• f946449: 8366178: Implement JEP 526: Lazy Constants (Second Preview)
• ... and 32 more: https://git.openjdk.org/jdk/compare/7d35a283cf2497565d230e3d5426f563f7e5870d...master

Your commit was automatically rebased without conflicts.

[openjdk]

@YaSuenag Pushed as commit dcba014.

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