On Mon, 18 Mar 2024 22:51:55 GMT, Claes Redestad 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.
>>
>> This PR passes tier1-3 tests.
>
>>
On Mon, 18 Mar 2024 14:09:09 GMT, Per Minborg 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.
>
> This PR passes tier1-3 tests.
> Initialization
On Mon, 18 Mar 2024 14:35:06 GMT, Claes Redestad wrote:
> 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
On Mon, 18 Mar 2024 14:09:09 GMT, Per Minborg 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,
On Mon, 18 Mar 2024 14:09:09 GMT, Per Minborg 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.
Nice Cleanup.
-
Marked as reviewed by
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.
-
Commit messages:
- Update copyright years
- Remove native method
Changes:
