JDK-8288094 : cleanup old _MSC_VER handling
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 19
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2022-06-09
  • Updated: 2024-10-18
  • Resolved: 2022-06-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 17 JDK 20
17-pool-oracleUnresolved 20 b02Fixed
Related Reports
Relates :  
JDK-8342639 - Global operator new in adlc has wrong exception spec
Description
We still handle at a number of places ancient historic _MSC_VER  versions of Visual Studio releases e.g. pre VS2013 (VS2013  has _MSC_VER 1800).
This should be cleaned up, as long as it is not 3rd party code that we don't want to adjust.

Currently still supported ("valid") VS version are 2017+, see  https://github.com/openjdk/jdk/blob/master/make/autoconf/toolchain_microsoft.m4 .
VALID_VS_VERSIONS="2019 2017 2022"
Comments
Changeset: 0530f4e5 Author: Matthias Baesken <mbaesken@openjdk.org> Date: 2022-06-14 10:43:07 +0000 URL: https://git.openjdk.org/jdk/commit/0530f4e517be5d5b3ff10be8a0764e564f068c06
14-06-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/9105 Date: 2022-06-09 11:37:21 +0000
09-06-2022