Assert in oopRecorder while compiling Graal
Tom Rodriguez
tom.rodriguez at oracle.com
Tue Oct 14 18:32:54 UTC 2014
I removed the duplicate check so it should be ok now.
tom
On Oct 13, 2014, at 2:37 PM, Tom Rodriguez <tom.rodriguez at oracle.com> wrote:
> This is an assert I recently added while fixing long code install times for graal. It should be true for graal generated code now and seemed to be true for c1/c2 code so I left it in there. It looks like in certain conditions it isn’t Anyway, I’ll modify the assert.
>
> tom
>
> On Oct 13, 2014, at 2:30 PM, Eric Caspole <eric.caspole at amd.com> wrote:
>
>> Hi everybody,
>> Since about last Thursday night my nightly Jenkins is getting new asserts like this:
>>
>> # Internal Error (/home/ecaspole/views/graal-default/graal/src/share/vm/code/oopRecorder.cpp:42), pid=21514, tid=140271113053952
>> # assert(false) failed: duplicate found
>>
>>
>> This is happening in C2 while compiling Graal code itself, while running the HSAIL tests.
>>
>> Usually:
>>
>> Current CompileTask:
>> C2: 90345 17862 4 com.oracle.graal.compiler.alloc.LinearScan::assignLocations (224 bytes)
>>
>>
>> Occasionally:
>>
>> Current CompileTask:
>> C2: 91131 17255 ! 4 com.oracle.graal.compiler.gen.NodeLIRBuilder::doBlock (478 bytes)
>>
>>
>> This happens about half the time when I run the tests like below with debug or fastdebug build:
>>
>> ./mx.sh --vm server --vmbuild debug unittest -server -ea -esa -XX:-UseHSAILDeoptimization -XX:-UseCompressedOops hsail.test
>>
>> We haven't changed anything lately. Thanks for any advice.
>> Eric
>
More information about the graal-dev
mailing list