Mon, September 19, 2011, 07:32 PM under GPGPU
One of the FAQs we receive is whether C++ AMP can be used to target the CPU.
For targeting multi-core we have a technology we released with VS2010 called PPL, which has had enhancements for VS 11 – that is what you should be using! FYI, it also has a Linux implementation via Intel's TBB which conforms to the same interface.
When you choose to use C++ AMP, you choose to take advantage of massively parallel hardware, through accelerators like the GPU.
Having said that, you can always use the accelerator class to check if you are running on a system where the is no hardware with a DirectX 11 driver, and decide what alternative code path you wish to follow.
In fact, if you do nothing in code, if the runtime does not find DX11 hardware to run your code on, it will choose the WARP accelerator which will run your code on the CPU, taking advantage of multi-core and SSE2 (depending on the CPU capabilities WARP also uses SSE3 and SSE 4.1 – it does not currently use AVX and on such systems you hopefully have a DX 11 GPU anyway).
A few things to know about WARP
- It is our fallback CPU solution, not intended as a primary target of C++ AMP.
- WARP stands for Windows Advanced Rasterization Platform and you can read old info on this MSDN page on WARP.
- What is new in Windows 8 Developer Preview is that WARP now supports DirectCompute, which is what C++ AMP builds on.
- It is not currently clear if we will have a CPU fallback solution for non-Windows 8 platforms when we ship.
- When you create a WARP accelerator, its is_emulated property returns true.
- WARP does not currently support double precision.
BTW, when we refer to WARP, we refer to this accelerator described above. If we use lower case "warp", that refers to a bunch of threads that run concurrently in lock step and share the same instruction. In the VS 11 Developer Preview, the size of warp in our Ref emulator is 4 – Ref is another emulator that runs on the CPU, but it is extremely slow not intended for production, just for debugging.