In this post, I’ll describe how C++ AMP projections can be used to write clear code that is easy to read and easy to maintain. Projections are a special case of C++ AMP sections that involve a rank change. They apply to both array and array_view objects, which we will collectively call arrays unless the distinction is important.
Before looking at projections, let’s briefly discuss indexing into arrays to get a single array element. You can index into arrays of rank N by passing N integers to the function call operator, (), or by passing an index object of rank N to the array subscript operator, .
Projections extend indexing to allow passing a single integer value to the array subscript operator of a multidimensional array. A projection of an array or array_view of rank N is an array_view of rank N-1 consisting of all of the elements with the most significant index equal to the single integer value. Since the result is an array_view, no data is copied. For example, the result of projecting a 2D array with integer i is the ith row (a 1D array_view). Here is a picture:
Let’s take a look at matrix-vector multiplication to see how we can use a projection to make the code easier to read. The following function implements a straight-forward, but simplistic, algorithm for matrix-vector multiplication in C++ AMP:
void mvm(array_view<const float,2> Matrix, // Input matrix
This simple code is a good candidate for using an array projection to improve clarity. Simply replace lines 10—17 of the above code with the following (differences are highlighted):
int y = idx;
In this code, we use a projection to create the named variable MatrixRow on line 11; this makes it clear that each thread is operating over only a single row of Matrix. Then on line 15, we can index into MatrixRow with integer x. By the way, if you find writing/reading the type array_view<const float,1> unfortunate, this would be a good place to use C++’s new auto feature and replace this type specification by the keyword auto, i.e., rewrite line 11 as follows:
auto MatrixRow = Matrix[y];
Like sections in C++ AMP, projections simplify the programming of many common idioms by making the code easier to understand.
Before I end this post, let me address a few miscellaneous points.
Cascading multiple projections
You can use multiple projections instead of multidimensional indexing, but the multidimensional indexing is stylistically preferable. For example, you could write arr_3d[i][j][k] instead of arr_3d(i, j, k). This amounts to projecting a 3D array to a 2D array_view, projecting the 2D array_view to a 1D array_view, and then indexing into the 1D array_view.
Changes from Visual Studio Developer Preview
In the Visual Studio Developer Preview version of C++ AMP, the array_view class defined a method called project with semantics identical to the above. In the Beta, this method was removed because we felt it was unnecessary.
The syntax of indexing
When it comes to indexing, the syntactic choices and guidance above are deliberate. Use the array subscript operator, , when indexing with index objects and when projecting with a single integer. Use the function call operator, (), when indexing with integers. These choices allow you to distinguish between projection and indexing only based on the type of the index. That said, the operators are completely interchangeable within the rules of the C++ language which do not allow the array subscript operator to be used with more than one expression.
As always, your feedback is welcome below or in our MSDN forum.