There should be an option that turns off the compact Strings functionality.
I.e. when user provides -XX:-ForceUTF16Strings, the implementation should default to UTF-16 unconditionally. This should serve as the safety net for users who experience performance regressions with compact strings. We have to investigate what is the best code shape for this kill switch to work in a performant way for both "on" and "off" modes.
I.e. when user provides -XX:-ForceUTF16Strings, the implementation should default to UTF-16 unconditionally. This should serve as the safety net for users who experience performance regressions with compact strings. We have to investigate what is the best code shape for this kill switch to work in a performant way for both "on" and "off" modes.
- relates to
-
JDK-8087309 Constant folding "static final boolean" in boolean expressions is incomplete
- Open
-
JDK-8130273 multiply -> shift reduction fails with complex control flow
- Open