RFR: AARCH64: optimize string compare intrinsic

Andrew Haley aph at redhat.com
Fri May 4 13:46:27 UTC 2018

On 05/04/2018 02:24 PM, Dmitrij Pochepko wrote:
> Do you suggest to change vectorizedMismatch from generic single entry 
> point to 4 versions (1,2,4 and 8 -byte) each optimized for respective 
> size(and possible re-using code generation logic)? Then it can be 
> re-used for same-encoded strings without penalties, indeed, but it 
> requires changes in jdk.internal.util.ArraysSupport.java

I don't see why it's absolutely necessary.  On the other hand, it might
be an excellent idea to have a switch statement in the Java code wich
will almost always optimized away.  It's worth trying.

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the hotspot-compiler-dev mailing list