[Parallel_libs-commits] [parallel-libs] r279855 - [StreamExecutor] Fix KernelSpec Doxygen

[Jason Henline via Parallel_libs-commits]

Author: jhen
Date: Fri Aug 26 14:55:32 2016
New Revision: 279855

URL: http://llvm.org/viewvc/llvm-project?rev=279855&view=rev
Log:
[StreamExecutor] Fix KernelSpec Doxygen

Summary:
There was a typo where \endcode was spelled as \encode and it was
keeping the whole file document from rendering. I also added in some \c
annotations for inline code stuff to make it look nicer.

Reviewers: jprice

Subscribers: parallel_libs-commits

Differential Revision: https://reviews.llvm.org/D23941

Modified:
    parallel-libs/trunk/streamexecutor/include/streamexecutor/KernelSpec.h

Modified: parallel-libs/trunk/streamexecutor/include/streamexecutor/KernelSpec.h
URL: http://llvm.org/viewvc/llvm-project/parallel-libs/trunk/streamexecutor/include/streamexecutor/KernelSpec.h?rev=279855&r1=279854&r2=279855&view=diff
==============================================================================
--- parallel-libs/trunk/streamexecutor/include/streamexecutor/KernelSpec.h (original)
+++ parallel-libs/trunk/streamexecutor/include/streamexecutor/KernelSpec.h Fri Aug 26 14:55:32 2016
@@ -31,9 +31,9 @@
 /// the user. A simplified example workflow which a compiler might follow in the
 /// case of a CUDA kernel that is compiled to CUDA fatbin code is as follows:
 ///
-/// 1. The user defines a kernel function called UserKernel.
+/// 1. The user defines a kernel function called \c UserKernel.
 /// 2. The compiler compiles the kernel code into CUDA fatbin data and embeds
-///    that data into the host code at address __UserKernelFatbinAddress.
+///    that data into the host code at address \c __UserKernelFatbinAddress.
 /// 3. The compiler adds code at the beginning of the host code to instantiate a
 ///    MultiKernelLoaderSpec:
 ///    \code
@@ -43,16 +43,16 @@
 ///    \endcode
 /// 4. The compiler then adds code to the host code to add the fatbin data to
 ///    the new MultiKernelLoaderSpec, and to associate that data with the kernel
-///    name "UserKernel":
+///    name \c "UserKernel":
 ///    \code
 ///    namespace compiler_cuda_namespace {
 ///      UserKernelLoaderSpec.addCUDAFatbinInMemory(
 ///        __UserKernelFatbinAddress, "UserKernel");
 ///    } // namespace compiler_cuda_namespace
-///    \encode
+///    \endcode
 /// 5. The host code, having known beforehand that the compiler would initialize
 ///    a MultiKernelLoaderSpec based on the name of the CUDA kernel, makes use
-///    of the symbol cudanamespace::UserKernelLoaderSpec without defining it.
+///    of the symbol \c cudanamespace::UserKernelLoaderSpec without defining it.
 ///
 /// In the example above, the MultiKernelLoaderSpec instance created by the
 /// compiler can be used by the host code to create StreamExecutor kernel