Re: RFR: 8359424: Eliminate table lookup in Integer/Long toHexString [v2]

2025-07-13 Thread Shaojin Wen
On Sun, 15 Jun 2025 05:53:26 GMT, Shaojin Wen wrote: >> In PR #22928, UUID introduced long-based vectorized hexadecimal to string >> conversion, which can also be used in Integer::toHexString and >> Long::toHexString to eliminate table lookups. The benefit of eliminating >> table lookups is th

Re: RFR: 8360459: UNICODE_CASE and character class with non-ASCII range does not match ASCII char

2025-07-13 Thread Chen Liang
On Mon, 14 Jul 2025 04:53:13 GMT, Xueming Shen wrote: > Regex class should conform to **_Level 1_** of [Unicode Technical Standard > #18: Unicode Regular Expressions](http://www.unicode.org/reports/tr18/), plus > RL2.1 Canonical Equivalents and RL2.2 Extended Grapheme Clusters. > > This PR pri

RFR: 8360459: UNICODE_CASE and character class with non-ASCII range does not match ASCII char

2025-07-13 Thread Xueming Shen
Regex class should conform to **_Level 1_** of [Unicode Technical Standard #18: Unicode Regular Expressions](http://www.unicode.org/reports/tr18/), plus RL2.1 Canonical Equivalents and RL2.2 Extended Grapheme Clusters. This PR primarily addresses conformance with RL1.5: Simple Loose Matches, whi

Re: RFR: 8361635: Missing List length validation in the Class-File API [v2]

2025-07-13 Thread Chen Liang
> The `class` file format often only stores lists up to 65535 in size because > size is encoded as a u2. Currently, we truncate the list size and write all > contents, creating malformed `class` files. Almost all scenarios where such > oversized lists are created can be considered an error; we s

Re: RFR: 8361614: Missing sub-int value validation in the Class-File API [v3]

2025-07-13 Thread Chen Liang
> In the `class` file format, a lot of the values are `u1` or `u2`; the > Class-File API consistently model them with `int`. However, the API does not, > in general, validate that int values passed to the factory methods are not > out of the bounds as defined in the class file format. This patch

Withdrawn: 8342382: Implementation of JEP G1: Improve Application Throughput with a More Efficient Write-Barrier

2025-07-13 Thread duke
On Sun, 23 Feb 2025 18:53:33 GMT, Thomas Schatzl wrote: > Hi all, > > please review this change that implements (currently Draft) JEP: G1: > Improve Application Throughput with a More Efficient Write-Barrier. > > The reason for posting this early is that this is a large change, and the JEP

Re: RFR: 8360575: java.util.Properties.list() methods trim each value to 37 characters in the listed output [v4]

2025-07-13 Thread Chen Liang
On Mon, 30 Jun 2025 06:01:44 GMT, Jaikiran Pai wrote: >> Can I please get a review of this doc-only change which proposes to clarify >> the current implementation of the `java.util.Properties.list(...)` methods? >> >> As noted in https://bugs.openjdk.org/browse/JDK-8360575, the current >> impl