-
Bug
-
Resolution: Unresolved
-
P3
-
None
-
In Review
This patch contains a set of changes to improve static builds. They will pave the way for implementing a full static-only java launcher. The changes here will:
1) Make sure non-exported symbols are made local in the static libraries. This means that the risk of symbol conflict is the same for static libraries as for dynamic libraries (i.e. in practice zero, as long as a consistent naming scheme is used for exported functions).
2) Remove the work-arounds to exclude duplicated symbols.
3) Fix some code in hotspot and the JDK libraries that did not work properly with a static java launcher.
The latter fixes are copied from or inspired by the work done by Jiangli Zhou and her team as part of the Project Leyden Hermetic Java.
1) Make sure non-exported symbols are made local in the static libraries. This means that the risk of symbol conflict is the same for static libraries as for dynamic libraries (i.e. in practice zero, as long as a consistent naming scheme is used for exported functions).
2) Remove the work-arounds to exclude duplicated symbols.
3) Fix some code in hotspot and the JDK libraries that did not work properly with a static java launcher.
The latter fixes are copied from or inspired by the work done by Jiangli Zhou and her team as part of the Project Leyden Hermetic Java.
- duplicates
-
JDK-8310491 Resolve some startup failures with JDK static build support
- Closed
- links to
-
Review(master) openjdk/jdk/19478