On Tue, 10 Dec 2024 07:30:19 GMT, Per Minborg wrote:
>> This PR proposes to fix a performance regression (on x64 platforms) for
>> 32-bit strings introduced by
>> [JDK-8345120](https://bugs.openjdk.org/browse/JDK-8345120).
>>
>> The PR also fixes a performance regression in the benchmarks caus
> This PR proposes to fix a performance regression (on x64 platforms) for
> 32-bit strings introduced by
> [JDK-8345120](https://bugs.openjdk.org/browse/JDK-8345120).
>
> The PR also fixes a performance regression in the benchmarks caused by using
> the wrong type for `MemorySegment`.
>
> Regr
On Thu, 5 Dec 2024 11:43:16 GMT, Per Minborg wrote:
>> This PR proposes to fix a performance regression (on x64 platforms) for
>> 32-bit strings introduced by
>> [JDK-8345120](https://bugs.openjdk.org/browse/JDK-8345120).
>>
>> The PR also fixes a performance regression in the benchmarks cause
> This PR proposes to fix a performance regression (on x64 platforms) for
> 32-bit strings introduced by
> [JDK-8345120](https://bugs.openjdk.org/browse/JDK-8345120).
>
> The PR also fixes a performance regression in the benchmarks caused by using
> the wrong type for `MemorySegment`.
>
> Regr
> This PR proposes to fix a performance regression (on x64 platforms) for
> 32-bit strings introduced by
> [JDK-8345120](https://bugs.openjdk.org/browse/JDK-8345120).
>
> The PR also fixes a performance regression in the benchmarks caused by using
> the wrong type for `MemorySegment`.
>
> Regr
On Wed, 4 Dec 2024 14:14:10 GMT, Jorn Vernee wrote:
> What are 'quad-string words'? FWIW, the word 'word' is somewhat ambiguous
> (although most people seem to interpret it as the size of an address), so you
> might want to specify in terms of bits/bytes instead.
Agreed. I've updated to "32-bi
On Wed, 4 Dec 2024 08:40:31 GMT, Per Minborg wrote:
> This PR proposes to fix a performance regression (on x64 platforms) for
> quad-string words introduced by
> [JDK-8345120](https://bugs.openjdk.org/browse/JDK-8345120).
>
> The PR also fixes a performance regression in the benchmarks caused