C++ AMP
native programming model that contains elements that span the C++ programming language and its runtime library; provides an easy way to write programs that compile and execute on data-parallel hardware (e.g. GPUs)
C++ Accelerated Massive Parallelism (C++ AMP) is a native programming model that contains elements that span the C++ programming language and its runtime library. It provides an easy way to write programs that compile and execute on data-parallel hardware, such as graphics cards and graphics processing units (GPUs).
Starting in Visual Studio 2022 (version 17.0), C++ AMP is declared as deprecated, indicating its end of support beyond Visual Studio 2022.
C++ AMP is a library implemented on DirectX 11 and an open specification from Microsoft for implementing data parallelism directly in C++. It is intended to make programming GPUs easy for the developer by supporting a range of expertise from none (in which case the system does its best) to being more finely controllable, but still portable. In Microsoft's implementation, code that cannot be run on GPUs will fall back onto one or more CPUs instead and use SSE instructions. The Microsoft implementation is included in Visual Studio 2012, including debugger and profiler support.
The initial C++ AMP release from Microsoft requires at least Windows 7 or Windows Server 2008 R2. As C++ AMP is an open specification, in time, implementations outside Microsoft should appear. One early example of this is Shevlin Park, Intel's experimental implementation of C++ AMP on Clang–LLVM and Open Computing Language (OpenCL).
“C++ AMP” enters the record as native programming model that contains elements that span the C++ programming language and its runtime library; provides an easy way to write programs that compile and execute on data-parallel hardware (e.g. GPUs). Crown Archives preserves that source wording while asking what native, programming and model can confirm, complicate or overturn.
Why this record matters
“C++ AMP” is worth following because a concise public description often conceals a longer documentary argument. Here, native, programming and model provides the most credible route into that argument.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated May 4, 2025. The linked authority identifier is Q722084. The first chronological checks are 2022, 2012 and 2008.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “C++ AMP”, its source revision and the description used here.
- Expand the search: follow C++ AMP primary sources, C++ AMP archive and native research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “C++ AMP”?
- What physical evidence or contemporary plan supports the description?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “C++ AMP” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.