Upcoming GPU backend changes

[Doug Simon]

Here’s a webrev for the first part of the changes described below:

http://cr.openjdk.java.net/~dnsimon/remove-HSAILCompilationResult/

-Doug

On Jan 22, 2014, at 10:10 PM, Doug Simon <doug.simon at oracle.com> wrote:

> Sure. I’ll post a webrev when I have one.
> 
> -Doug
> 
> On Jan 22, 2014, at 10:06 PM, Deneau, Tom <tom.deneau at amd.com> wrote:
> 
>> Doug --
>> 
>> It would be good if AMD could get access to this before it gets checked in
>> so we can give some feedback.  In particular, there are hsail-hardware based targets
>> which are not publicly available which we can test on.
>> 
>> -- Tom
>> 
>> 
>>> -----Original Message-----
>>> From: graal-dev-bounces at openjdk.java.net [mailto:graal-dev-
>>> bounces at openjdk.java.net] On Behalf Of Doug Simon
>>> Sent: Wednesday, January 22, 2014 2:24 PM
>>> To: sumatra-dev at openjdk.java.net; graal-dev at openjdk.java.net
>>> Subject: Upcoming GPU backend changes
>>> 
>>> Hi,
>>> 
>>> I've just created a JBS issue supporting multiple co-existing GPU
>>> backends: https://bugs.openjdk.java.net/browse/GRAAL-1
>>> 
>>> Prior to making the C++ changes need for this, I want to bring the HSAIL
>>> Java code more in alignment with the recently revised PTX backend.
>>> Namely:
>>> 
>>> 1. All compilation harness logic will be moved into HSAILHotSpotBackend
>>> (out of HSAILCompilationResult).
>>> 2. Create the equivalent of PTXWrapperBuilder for HSAIL. This is a
>>> generated stub that handles the transition from CPU to GPU and back. It
>>> also removes the need for the C++ HSAILKernelArguments class.
>>> 
>>> If you have any questions or concerns about this, please let me know
>>> asap. I'm happy to have a Skype call as well if that is desirable.
>>> 
>>> -Doug
>>> 
>>> 
>> 
>> 
>