On Mon, 18 Mar 2024 14:09:09 GMT, Per Minborg <pminb...@openjdk.org> wrote:
> This PR proposes to remove the native method `StringUTF16::isBigEndian` and > its corresponding C implementation and instead rely on the > `jdk.internal.misc.Unsafe::isBigEndian` method. Does this change how early `Unsafe` is initialized, and does it in turn have dependencies on `StringUTF16`? `StringUTF16` is loaded very early, especially if `-XX:-CompactStrings` is supplied and I would assume the only reason this was added in the first place was to avoid some bootstrapping issue. ------------- PR Comment: https://git.openjdk.org/jdk/pull/18348#issuecomment-2004086796