By adding the JVM startup parameters `-XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining` and analyzing the printed log information, and found that the code size of the j.t.f.DateTimePrintContext::adjust method is 382, which is greater than 325, causing inlining failure.
@ 7 java.time.format.DateTimePrintContext::adjust (382 bytes) failed to inline: hot method too big By splitting the code into `common/uncommon`, and moving the uncommon code into adjust0, the adjust method is kept small and can be inlined by the C2 optimizer. ------------- Commit messages: - from @jodastephen - from @jodastephen - Separate exception handling into two separate methods to make codeSize < 325 Changes: https://git.openjdk.org/jdk/pull/26633/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=26633&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8365186 Stats: 22 lines in 1 file changed: 21 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/26633.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/26633/head:pull/26633 PR: https://git.openjdk.org/jdk/pull/26633
