| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8313247 | 17-pool-oracle | Rajat Mahajan | P4 | Open | Unresolved |
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"
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"
- backported by
-
JDK-8313247 cleanup old _MSC_VER handling
-
- Open
-
- relates to
-
JDK-8342639 Global operator new in adlc has wrong exception spec
-
- Open
-
