Update SYCL component for oneAPI 1.2 release (#429)

* Remove unused template names

* Simplify the DPC++ component

Simplify the description of the the DPC++ component.  We only need to
state that DPC++ is a combination of SYCL and a certain set of SYCL
extensions.  Remove the "test" column of the extension table since
most entries are just N/A.

* Rename from DPC++ to SYCL

Rename the "DPC++" component to "SYCL".  We no longer refer to "DPC++"
as a specification in its own right.  Rather, DPC++ is the name of an
implementation of the SYCL spec.

* Update SYCL extension table

This is the list of "supported" extensions in the DPC++ 2022.2 compiler
release.  Pointers to extension documents are now a tagged URL, so the
oneAPI spec refers to a specific copy of the extension spec even if the
version in the DPC++ repo evolves over time.

Author: gmlueck

scripts/oneapi.py

@@ -284,7 +284,7 @@ def sort_words(root, target=None):
     'oneMKL',
     'oneTBB',
     'oneVPL',
-    'dpcpp',
+    'sycl',
     'l0',
     'oneDPL',
     'oneDNN',

source/architecture.rst

@@ -6,7 +6,7 @@ Software Architecture
 =====================
 
 oneAPI provides a common developer interface across a range of data
-parallel accelerators (see the figure below).  Programmers use DPC++
+parallel accelerators (see the figure below).  Programmers use SYCL
 for both API programming and direct programming.  The capabilities of
 a oneAPI platform are determined by the Level Zero interface, which
 provides system software a common abstraction for a oneAPI device.
@@ -89,7 +89,7 @@ API Programming Example
 
 API programming requires the programmer to specify the target device and the
 memory communication strategy.  In the following example, we call the
-oneMKL matrix multiply routine, GEMM.  We are writing in DPC++ and
+oneMKL matrix multiply routine, GEMM.  We are writing in SYCL and
 omitting irrelevant details.
 
 We create a queue initialized with a *gpu_selector* to specify that we
@@ -136,7 +136,7 @@ With direct programming, we specify the target device and the memory
 communication strategy, as we do for API programming.  In addition, we
 must define and submit a command group to perform the computation.
 In the following example, we write a simple data parallel matrix
-multiply.  We are writing in DPC++ and omitting irrelevant
+multiply.  We are writing in SYCL and omitting irrelevant
 details.
 
 We create a queue initialized with a *gpu_selector* to specify that the

source/conf/common_conf.py

@@ -53,8 +53,6 @@
 
 prolog_template = string.Template(
     r"""
-.. |dpcpp_full_name| replace:: oneAPI Data Parallel C++
-.. |dpcpp_version| replace:: $oneapi_version
 .. |dpl_full_name| replace:: oneAPI DPC++ Library
 .. |dpl_version| replace:: $oneapi_version
 .. |ccl_full_name| replace:: oneAPI Collective Communications Library

source/elements/dpcpp/source/index.rst

@@ -2,8 +2,8 @@
 ..
 .. SPDX-License-Identifier: CC-BY-4.0
 
-- :ref:`oneDPCPP-section`: oneAPI's core language for programming
-  accelerators and multiprocessors. DPCPP allows developers to reuse
+- :ref:`sycl-section`: oneAPI's core language for programming
+  accelerators and multiprocessors. SYCL allows developers to reuse
   code across hardware targets (CPUs and accelerators such as GPUs and
   FPGAs) and tune for a specific architecture
 - :ref:`oneDPL-section`: A companion to the DPC++ Compiler for

source/elements/element_list.rst

@@ -21,7 +21,7 @@
 from os.path import join
 
 
-project = 'dpcpp'
+project = 'sycl'
 
 repo_root = join('..', '..', '..', '..')
 exec(open(join(repo_root, 'source', 'conf', 'common_conf.py')).read())