Tom Stellard <[email protected]> writes:

> On Wed, May 23, 2012 at 02:04:20PM +0200, Francisco Jerez wrote:
>>[...]
>> Do we need this compatibility code?  Don't you have to build a patched
>> version of LLVM from sources for this to work anyway?
>> 
>
> You only need a patch if you want to use the r600 target.  This
> compatibility code is necessary if you want to generate code for other
> targets.  I don't mind dropping it, but it would mean that clover won't
> work with LLVM versions older than 3.1
>
That's fine...  In any case, r600 is the only working LLVM target we're
going to have once these changes are applied.

>>[...]
>> > +            /* XXX: Figure out LLVM->OpenCL address space mappings for 
>> > each
>> > +             * target.  I think we need to ask clang what these are.  For 
>> > now,
>> > +             * pretend everything is in the global address space. */
>> 
>> Aren't these supposed to be defined arbitrarily by the standard library
>> using "address_space" attributes?
>> 
>
> The OpenCL address space mappings are one of the attributes of a target
> in Clang, they aren't defined in the standard library.
>

OK, makes sense.

Attachment: pgpuiN2iNjqvZ.pgp
Description: PGP signature

_______________________________________________
mesa-dev mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to