On Mon, 21 Feb 2022 18:13:12 GMT, Phil Race <p...@openjdk.org> wrote:
> As per the bug evaluation, the root of this issue is that on this platform > "char" is treated as "unsigned char" > and the code here expects it to be "signed char", so we need to make it > explicitly so. > For all other supported platforms this is a no-op since that is the default > elsewhere. > So this should be a safe fix, and the updated JDK has been tested on all > platforms. Marked as reviewed by dmarkov (Reviewer). ------------- PR: https://git.openjdk.java.net/jdk/pull/7563
