-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b18
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8323367 | 21.0.3-oracle | Andrew Leonard | P4 | Resolved | Fixed | b01 |
JDK-8319823 | 21.0.2 | Andrew Leonard | P4 | Resolved | Fixed | b07 |
When doing a reproducible Windows build on two different machines, that
happen to have MS Visual Studio installed in different paths, the resulting
builds are not identical.
The reason is due to the System include paths, eg:
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\include\vcruntime_new.h
appearing in the compiler obj as part of debug info.
For non-Absolute path builds, these need to be -pathmap'd
happen to have MS Visual Studio installed in different paths, the resulting
builds are not identical.
The reason is due to the System include paths, eg:
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\include\vcruntime_new.h
appearing in the compiler obj as part of debug info.
For non-Absolute path builds, these need to be -pathmap'd
- backported by
-
JDK-8319823 Windows builds are not reproducible if MS VS compiler install path differs
-
- Resolved
-
-
JDK-8323367 Windows builds are not reproducible if MS VS compiler install path differs
-
- Resolved
-
- relates to
-
JDK-8317601 Windows build on WSL broken after JDK-8317340
-
- Resolved
-
- links to
-
Commit openjdk/jdk21u/5cb041eb
-
Commit openjdk/jdk/353d1396
-
Review openjdk/jdk21u/313
-
Review openjdk/jdk/16008
(2 links to)