search for: __private

..., and we already have > > mechanisms in the frontend that could be used to solve the second. > > > > Which mechanisms could be used to differentiate between thread-private and > __local data? In OpenCL C, it is illegal to declare a variable with static storage duration in the __private address space (section 6.5: "All program scope variables must be declared in the __constant address space."; section 6.8g: "The extern, static, auto and register storage-class specifiers are not supported."). This implies that there is no way for pointers to the __private addre...

...isms in the frontend that could be used to solve the second. > > > > > > > Which mechanisms could be used to differentiate between thread-private > and > > __local data? > > In OpenCL C, it is illegal to declare a variable with static storage > duration in the __private address space (section 6.5: "All program > scope variables must be declared in the __constant address space."; > section 6.8g: "The extern, static, auto and register storage-class > specifiers are not supported."). This implies that there is no way > for pointers to...

On Thu, Oct 13, 2011 at 11:57 AM, Peter Collingbourne <peter at pcc.me.uk>wrote: > 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

...o make children in the tree alias each other. > > Additionally, the last address space is marked as constant which could > be used for optimization, e.g. LICM. You mean that 1, 2, 3 do not alias each other, but they all alias with 0, right? The address space 0 in used to represent opencl __private address space, I think it would not alias with the others... BTW, I like the approach: it allows a fine description of relationship between address spaces that can be used in the middle-end, and the frontend is responsible for the correct emission of this language specific information. That...

...tree alias each other. >> >> Additionally, the last address space is marked as constant which could >> be used for optimization, e.g. LICM. > > You mean that 1, 2, 3 do not alias each other, but they all alias with 0, right? The address space 0 in used to represent opencl __private address space, I think it would not alias with the others… Yeah, thats right, i have them all alias 0. If 0 is private and doesn’t alias anything then thats even better. Potentially that means that the optimizer will be able to reorder any access to globals with any other access to the stack for...

On Tue, Mar 1, 2011 at 4:06 PM, David Neto wrote: > On Mon, Feb 28, 2011 at 4:41 PM, Peter Collingbourne wrote: >> >> The more I think about it, the more I become uncomfortable with the >> concept of language-specific address spaces in LLVM.  These are the >> main issues I see with language-specific address spaces: > > ... > >> Instead of language-specific

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

On Aug 7, 2013, at 2:07 PM, Matt Arsenault <Matthew.Arsenault at amd.com> wrote: > On 08/07/2013 01:52 PM, Michele Scandale wrote: >> >> IMHO this information should be a plus that could be *safely* ignored when not necessary and used where it can provide an improvement in optimizations. This does not necessary mean the the middle-end (and the back-ends) must be aware of the

...ress space saved in the IR. If in the IR we have the logical address space, somewhere else I expect to have the physical one (its recomputation may be fine). >> You mean that 1, 2, 3 do not alias each other, but they all alias with 0, right? The address space 0 in used to represent opencl __private address space, I think it would not alias with the others… > Yeah, thats right, i have them all alias 0. If 0 is private and doesn’t alias anything then thats even better. Potentially that means that the optimizer will be able to reorder any access to globals with any other access to the stack...

...will you be generating ELF binaries with special metadata sections (This is what R600 currently does) or will you be creating your own object format. > * Fix handling of the multiple OpenCL address spaces. > (approx. July 8 - July 22) > > Operations on __global, __local, and __private memory will be > dealt with using the resource access opcodes, __kernel function > parameters will be accessed through a special resource meant for > parameter passing, __constant memory will be mapped to constant > buffers. > > * Get function calls working reli...

Francisco Jerez <currojerez at riseup.net> writes: >[...] > Pity not to see any interest in this since I brought up the idea two > weeks ago. I've uploaded a first attempt at writing a TGSI back-end > here [2]. It's able to generate code -- though only in assembly form > and with many loose ends still. > > Also, would it be possible for Tom Stellard

...ormat implemented in 'clover/core/module.cpp' seems to do everything we need, so another option would be to stick to it. > >> * Fix handling of the multiple OpenCL address spaces. >> (approx. July 8 - July 22) >> >> Operations on __global, __local, and __private memory will be >> dealt with using the resource access opcodes, __kernel function >> parameters will be accessed through a special resource meant for >> parameter passing, __constant memory will be mapped to constant >> buffers. >> >> * Get fun...

On Mon, Feb 28, 2011 at 4:41 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > The more I think about it, the more I become uncomfortable with the > concept of language-specific address spaces in LLVM.  These are the > main issues I see with language-specific address spaces: ... > Instead of language-specific address spaces, each target should > concentrate on

On Fri, Feb 25, 2011 at 02:55:33PM -0500, Ken Dyck wrote: > The address space mechanism is used by some code generators to > differentiate between physical memory spaces. The PIC16 code generator > uses address spaces 0 and 1 to select between its RAM and ROM spaces. > And X86 uses address space 256 for GS and 257 for FS. In the back end > for a dual-harvard DSP that I've been

...tart would be to look at the PureStreamer class and figure out what additional features you might need. > > > >> * Fix handling of the multiple OpenCL address spaces. > >> (approx. July 8 - July 22) > >> > >> Operations on __global, __local, and __private memory will be > >> dealt with using the resource access opcodes, __kernel function > >> parameters will be accessed through a special resource meant for > >> parameter passing, __constant memory will be mapped to constant > >> buffers. > >&...