Hi Claes,
Some observations:
394 int u1 = CharacterDataLatin1.instance.toUpperCase(c1);
395 int u2 = CharacterDataLatin1.instance.toUpperCase(c2);
Changing u1 & u2 from char -> int, L399 now calls toLowerCase(int)
instead of toLowerCase(char). Should be fine, though. Speaking of:
399
On 2019-08-09 02:41, Jim Laskey wrote:
+1
Thanks, Jim!
/Claes
+1
> On Aug 8, 2019, at 8:28 AM, Claes Redestad wrote:
>
> Hi,
>
> in j.l.StringLatin1 we can and do call CharacterDataLatin1 directly in
> some places, which avoids a few indirections. Doing so has no effect on peak
> performance, but simplifies the work the JIT needs to do and speeds
> up
Hi,
in j.l.StringLatin1 we can and do call CharacterDataLatin1 directly in
some places, which avoids a few indirections. Doing so has no effect on
peak performance, but simplifies the work the JIT needs to do and speeds
up a variety of operations during startup and warmup.
