mx vm server option
doug.simon at oracle.com
Fri May 3 03:15:21 PDT 2013
On May 3, 2013, at 12:15 AM, "Venkatachalam, Vasanth" <Vasanth.Venkatachalam at amd.com> wrote:
> One of our test cases works when run without the -vm server option but fails when run with this option.
> The code generated when this option is enabled is different and we don't yet understand why.
Could you please provide more detail on how your test case fails and what is different about the generated code.
> Are there any changes triggered by this option which could account for these differences?
Not that I'm aware of.
> Also have there been any recently introduced changes which affect what this option does? Our test case used to work with and without this option before we merged with the latest trunk.
I pushed one change yesterday that fixed an issue with Catch_StackOverflowError_01. It triggered when C2 compiled code threw an exception that unwound to Graal compiled code. The (new) exception handler stub in Graal asserts that the exception PC stored in the current thread is 0 and this assertion was failing.
More information about the graal-dev