-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b19
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8287564 | 17.0.4 | Andrew Leonard | P4 | Resolved | Fixed | b05 |
FIx JDK-8284437 resolved reproducible builds from different workspaces,
but utilized relative path linking because assembly files embedded absolute
file paths during the library linking.
The embedded absolute assembly file path symbols is because the source
.S assembly files do not specify a .file symbol location, which then means
the linker embeds a symbol link to the absolute .object file.
Usage of a .file <relative source location> in the .S source will result in a
correct .file symbol.
but utilized relative path linking because assembly files embedded absolute
file paths during the library linking.
The embedded absolute assembly file path symbols is because the source
.S assembly files do not specify a .file symbol location, which then means
the linker embeds a symbol link to the absolute .object file.
Usage of a .file <relative source location> in the .S source will result in a
correct .file symbol.
- backported by
-
JDK-8287564 Reproducible assembly builds without relative linking
-
- Resolved
-
- relates to
-
JDK-8284437 Building from different users/workspace is not always deterministic
-
- Resolved
-