RFR(S) : 8043125 : compiler/types/correctness/CorrectnessTest.java: assert(layout->tag() == DataLayout::speculative_trap_data_tag) failed: wrong type
igor.ignatyev at oracle.com
Wed Nov 5 10:57:31 UTC 2014
actually, I've already pushed this. However before that, I ran modified
'types/correctness/CorrectnessTest.java' to check the case similar to
the one which you described : w/ the extra thread which calls
WB.ClearMethodState in the loop. And I didn't get any failures, so it
looks like it's safe.
if we bump into problem w/ that, I'll return VM operation.
On 11/03/2014 04:08 PM, Roland Westrelin wrote:
> Wouldn’t it be better to keep the VM operation? If there’s java code running concurrently with the ClearMethodState call, profile will be updated and cleared concurrently. I’m not sure that would be safe. Or are we sure that ClearMethodState will never be run concurrently with other code?
More information about the hotspot-compiler-dev