Zoltán Gilián writes:
>> Whether you need to pass the image
>> dimensions and data type to the kernel as explicit parameters or not
>> (e.g. because your hardware already supports some sort of image metadata
>> query opcode) is driver-specific, so it would probably be a better idea
>> to append t
> Whether you need to pass the image
> dimensions and data type to the kernel as explicit parameters or not
> (e.g. because your hardware already supports some sort of image metadata
> query opcode) is driver-specific, so it would probably be a better idea
> to append these parameters at the end of
Ok, thanks for the feedback.
On Mon, Jun 8, 2015 at 2:18 PM, Francisco Jerez
wrote:
> Zoltan Gilian writes:
>
> > Image attributes are passed to the kernel as hidden parameters after the
> > image attribute itself. An llvm pass replaces the getter builtins to
> > the appropriate parameters.
> >
Zoltan Gilian writes:
> Image attributes are passed to the kernel as hidden parameters after the
> image attribute itself. An llvm pass replaces the getter builtins to
> the appropriate parameters.
> ---
> src/gallium/state_trackers/clover/core/kernel.cpp | 13 ++
> src/gallium/state_trackers/
Image attributes are passed to the kernel as hidden parameters after the
image attribute itself. An llvm pass replaces the getter builtins to
the appropriate parameters.
---
src/gallium/state_trackers/clover/core/kernel.cpp | 13 ++
src/gallium/state_trackers/clover/core/memory.cpp | 2 +-
..
