Odd Loop x86 CodeGen Behavior

[Vladimir Kozlov]

Don't look on TraceSpilling now.
First, we need to know where stores in B10 are coming from.
Look what the ideal graph is generated before matcher.
You can use -XX:+PrintIdeal.

Vladimir

Edward Lee wrote:
> On Tue, Dec 9, 2008 at 3:29 PM, Vladimir Kozlov <Vladimir.Kozlov at sun.com> wrote:
>> The stack spills you see are generated by Register Allocator.
> Sorry, I wasn't clear in the original message, but ESP+64 is actually
> an input parameter.
> #r051 esp+68: parm 2: long
> #r050 esp+64: parm 2: long
> 
> I noticed I could set TraceSpilling option in hotspot_compiler, but
> I'm not familiar with that output. Should I be looking at that output?
> 
>> Do you have a small test to show this problem?
> I suppose it isn't possible to give the ideal node graph and
> reconstruct from there? I'll see if I can make a small java method
> that doesn't require the custom transformations I've got going on.
> 
> Ed