Displaying 4 results from an estimated 4 matches for "ssa_memory_spac".
Did you mean:
ssa_memory_space
2011 Oct 13
2
[LLVMdev] [cfe-dev] RFC: Representation of OpenCL Memory Spaces
...guage does not
contain support for address space qualified pointer types (only address
space qualified declarations). NVIDIA's CUDA compiler, nvopencc,
determines the correct address space for each pointer using type
inference (there is an explanation of nvopencc's algorithm in the
src/doc/ssa_memory_space.txt file in the nvopencc distribution).
Our compiler should eventually contain a similar algorithm.
Thanks,
--
Peter
2011 Oct 13
0
[LLVMdev] [cfe-dev] RFC: Representation of OpenCL Memory Spaces
...in support for address space qualified pointer types (only address
> space qualified declarations). NVIDIA's CUDA compiler, nvopencc,
> determines the correct address space for each pointer using type
> inference (there is an explanation of nvopencc's algorithm in the
> src/doc/ssa_memory_space.txt file in the nvopencc distribution).
> Our compiler should eventually contain a similar algorithm.
>
> Thanks,
> --
> Peter
>
--
Thanks,
Justin Holewinski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/...
2011 Oct 13
0
[LLVMdev] [cfe-dev] RFC: Representation of OpenCL Memory Spaces
Justin,
Out of these options, I would take the metadata approach for AA support.
This doesn't solve the problem of different frontend/backends choosing different
address space representations for the same language, but is the correct
approach for providing extra information to the optimizations.
The issue about memory spaces in general is a little different. For example, based on
the
2011 Oct 13
4
[LLVMdev] [cfe-dev] RFC: Representation of OpenCL Memory Spaces
Hi Justin,
Thanks for bringing this up, I think it's important to discuss
these issues here.
On Thu, Oct 13, 2011 at 09:46:28AM -0400, Justin Holewinski wrote:
> It is becoming increasingly clear to me that LLVM address spaces are not the
> general solution to OpenCL/CUDA memory spaces. They are a convenient hack to
> get things working in the short term, but I think a more