webrev for hsail compiler safepoints

[Christian Thalinger]

On Apr 15, 2014, at 11:23 AM, Caspole, Eric <Eric.Caspole at amd.com> wrote:

> Hi everybody,
> I put up a new webrev for supporting compiler safepoints in HSAIL. This is an incremental change using the HSAIL deoptimization feature, so if a safepoint is detected in the kernel it will deoptimize back to CPU to complete the workitems. This will help avoid long running loops in kernels from halting the CPU threads in the event a safepoint is required during the kernel execution.
> 
> http://cr.openjdk.java.net/~ecaspole/hsail_comp_safepoints/webrev/
> 
> There were already about 12 tests in the hsail tests that cause compiler safepoints to be emitted. Also we have an internal app with long running workitems which was a good test. I added a -XX:+UseHSAILSafepoints which is true by default, so we can experiment with it.

Of course it doesn’t matter that much in Graal but in general try to avoid adding product flags.  If something is experimental or for diagnostics use that flag type instead.  These can then be unlocked in a product build.

> Let me know your comments.
> Thanks,
> Eric
>