RFR: 8273278: Support XSLT on GraalVM Native Image--deterministic bytecode generation in XSLT

Jovan Stevanovic github.com+44313413+jovanstevanovic at openjdk.java.net
Tue Sep 7 04:17:49 UTC 2021

GraalVM Native Image supports loading classes at runtime if they are known during image build (class predefinition). This is achieved by the JVMTI agent that registers dynamically generated classes in a regular HotSpot run. The Native Image build uses these registered classes to embed them into the produced binary so they can be loaded at runtime. Loading at runtime is achieved by matching the unique hash of generated classes.

If the generated bytecode is unstable across runs, the generated native image can not match the hash of the runtime-generated bytecode to the pre-defined classes. The execution failure happens here:

In XSLT the produced bytecode is unstable for the following reasons:

- Methods like ` HashMap#values` and `HashMap#keySet` result in different traversal orders of its elements yielding a different order of methods and fields.

- The default `Object#toString` includes the current memory reference of `com.sun.org.apache.xalan.internal.xsltc.compiler.Number` in the generated class.


Commit messages:
 - 8273278: Improving XSLT support for GraalVM's Native Image.

Changes: https://git.openjdk.java.net/jdk/pull/5331/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=5331&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8273278
  Stats: 15 lines in 4 files changed: 5 ins; 0 del; 10 mod
  Patch: https://git.openjdk.java.net/jdk/pull/5331.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/5331/head:pull/5331

PR: https://git.openjdk.java.net/jdk/pull/5331

More information about the core-libs-dev mailing list