RFR: AARCH64: optimize string compare intrinsic

Andrew Haley aph at redhat.com
Fri May 4 12:59:42 UTC 2018

On 05/04/2018 12:28 PM, Dmitrij Pochepko wrote:
> vectorizedMismatch intrinsic contract moves type information from 
> compile time to runtime (to have single entry point), 

It does not have to do that: there's no reason not to be able to
use the same vectorized-mismatch-generating logic able to use
constant information (i.e. the type) conditionally at code gen

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