Is there any time schedule about the next APP SDK version? It's been about 6 months since the previous version was released.
Although I am not in direct need of the feature, SPIR support is not yet implemented in 2.8 if I'm not mistaken. During little mailing with Clang dev working on the C++AMP prototype inside the Clang compiler asked me whether I knew any platform that implemented SPIR compilation yet. As of now he implemented NVPTX frontend, but naturally SPIR would be better. (Since NV is not expected to implement SPIR compilation anytime soon, I'd expect both intermediates to be stored inside the binary for portability.)
Hi I expect to AMD to support all new OCL 1.2 extensions anounced late last year specially graphics ones (please at least can you gather expected ETA on graphics ones and what ones are going to be implemented?)
please provide this ones!
other interesting one:
and security ones would be good:
I would expect console support under linux without root (although this might be a GPU driver issue), linux zero copy support for older than GCN GPUs (am I expecting too much?) and an updated reference manual (covering Sea Islands changes).
ekondis, All these are really from the driver side. Not really from APP SDK.
As far as manual update for sea islands -- I will fwd your request.
Console support -- Driver team is already working on it.
Linux zero-copy suppor for non-GCN } - Do you mean to say windows supports and Linux does not? Can you elaborate?
read the programing guide table 4.2. CL_MEM_USE_PERSISTENT_MEM_AMD flag is supported on Windows Vista/7. On Linux only Southern Islands. Also driver version doesn't contain VM which AFAIK indicate zero copy support. and when we are at difference between Linux and Windows it will be nice if we could use whole VRAM on Linux as currently it is still limited to 50%.
A very long time ago someone tried to acquire depth buffers and failed to. I figured something like this would surely be solved in a matter of years. Now I see this feature is actually an OpenCL 1.2 extension. Since I'm about to implement Object Distributed Render, and I will need Z-composition roughly 3 weeks from now, if this feature would make it, that would rock. (I know if things go wrong I could always implement it in pixel shaders, but hey... since it's an interop app anyway...