aarch64 AD-file / matching rule

Andrew Haley aph at redhat.com
Tue May 12 16:59:14 UTC 2015


Hi,

On 04/23/2015 02:41 PM, Benedikt Wedenik wrote:

> I’m writing compiler-optimisations for the aarch64 port at the moment and I am using specjbb2005 for benchmarking.
> One of the patterns I want to optimise is the following:
> 
>   0x0000007f8c2961b4: andw2, w2, #0x7ffff8
>   0x0000007f8c2961b8: cmpw2, #0x0
>   0x0000007f8c2961bc: b.eq0x0000007f8c2968f4

I do not see this pattern generated anywhere by C2.  If you can tell
me which routine is being compiled I will be very interested.

It is generated a lot by C1, but that's C1: not interesting.

Incidentally, if you want to see a profile of specjbb2005, do this:

operf java -Xms256m -Xmx256m -agentpath:/usr/lib64/oprofile/libjvmti_oprofile.so spec.jbb.JBBmain -propfile SPECjbb.props

then, afterwards:

opreport -l

Andrew.



More information about the hotspot-compiler-dev mailing list