You know very well that even if he posts 5 apps they are close to nothing compared to hundreds of OpenCl apps available today.
Everyone was touting about AVX and 256bit AVX before Haswell release, where are the apps today ??? Nobody even mentioned AVX again since then
I will not use the F word, the Intel supporters
Is it that personal for you?
Then load up on AMD stock...
BTW, nobody will take over AMD. Apple poached all of the CPU and GPU talent that it needed from the AMD school, and Samsung got a bunch too. Nobody wants a debt laden firm that can hardly compete in its core markets.
I will say all these talks have been enlightening about why PS4 and Xbone went with what most consider an anemic cpu. It seems these developers are not worried about it.
Digital Foundry: So often you're CPU bound. That explains why so many of the Data Move Engine functions seem to be about offloading CPU?
Andrew Goossen: Yeah, again I think we under-balanced and we had that great opportunity to change that balance late in the game. The DMA Move Engines also help the GPU significantly as well. For some scenarios there, imagine you've rendered to a depth buffer there in ESRAM. And now you're switching to another depth buffer. You may want to go and pull what is now a texture into DDR so that you can texture out of it later and you're not doing tons of reads from that texture so it actually makes more sense for it to be in DDR. You can use the Move Engines to move these things asynchronously in concert with the GPU so the GPU isn't spending any time on the move. You've got the DMA engine doing it. Now the GPU can go on and immediately work on the next render target rather than simply move bits around.
Nick Baker: From a power/efficiency standpoint as well, fixed functions are more power-friendly on fixed function units. We put data compression on there as well, so we have LZ compression/decompression and also motion JPEG decode which helps with Kinect. So there's a lot more than to the Data Move Engines than moving from one block of memory to another.
The good information is that they are not tied to GCN and can abandon it for some new architecture and still retain mantle compatibility. At first a lot of people were concerned that it would slow their GPU innovation due to inability to move from GCN. IMHO NV is too boneheaded to adopt mantle which is a shame I'd like to have some speed-up just from new API but I'm 99.9% sure it's not going to happen. They even limit their own gpu sales by blocking PsyX on systems that have AMD card as main rendering card and NV card as PsyX card, not to mention allow AMD cards to do their own PsyX computations. JHH should go. Imagine NV with no wooden-screws or dissapearing dragons. Yeah, I can't too