RFR(XS) 8046289: compiler/6340864/TestLongVect.java timeout with
vladimir.x.ivanov at oracle.com
Mon Jun 30 16:15:21 UTC 2014
Why do you make a special case for loop exit here? I'd expect more
general solution to trust scarce profile data more in -Xcomp mode.
Some background: Tobias and me have been looking at JDK-8014830  and
JDK-8030976 fixed the problem. I suspect that this change will return
On 6/30/14 11:26 AM, Rickard Bäckman wrote:
> Reviews please?
> On 06/23, Rickard Bäckman wrote:
>> a test started to timeout after JDK-8030976 was pushed. The test was run
>> with -Xcomp flag, so the profiling data available is non-existing or
>> small. For some cases that meant that if a loop had at least 1 iteration
>> executed it would look like the loop would always take the backedge and
>> never end and we would generate an uncommon trap on the loop exit.
>> The small change checks if the block we are considering turning into an
>> uncommon trap is a loop exit.
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8046289
>> Webrev: http://cr.openjdk.java.net/~rbackman/8046289/
More information about the hotspot-compiler-dev