mx vm server option
Vasanth.Venkatachalam at amd.com
Thu May 2 15:15:50 PDT 2013
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.
Are there any changes triggered by this option which could account for these differences?
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.
More information about the graal-dev