r262013 - Fixing an issue with the code block so that it does not appear as a list.

[Aaron Ballman via cfe-commits]

Author: aaronballman
Date: Fri Feb 26 07:39:38 2016
New Revision: 262013

URL: http://llvm.org/viewvc/llvm-project?rev=262013&view=rev
Log:
Fixing an issue with the code block so that it does not appear as a list.

Modified:
    cfe/trunk/include/clang/Basic/AttrDocs.td

Modified: cfe/trunk/include/clang/Basic/AttrDocs.td
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/include/clang/Basic/AttrDocs.td?rev=262013&r1=262012&r2=262013&view=diff
==============================================================================
--- cfe/trunk/include/clang/Basic/AttrDocs.td (original)
+++ cfe/trunk/include/clang/Basic/AttrDocs.td Fri Feb 26 07:39:38 2016
@@ -1583,10 +1583,8 @@ s6.11.5 for details.
 
 def OpenCLAccessDocs : Documentation {
   let Category = DocCatStmt;
-  let Heading = "__read_only, __write_only, __read_write (read_only, "
-                "write_only, read_write)";
-  let Content = [
-    {
+  let Heading = "__read_only, __write_only, __read_write (read_only, write_only, read_write)";
+  let Content = [{
 The access qualifiers must be used with image object arguments or pipe arguments
 to declare if they are being read or written by a kernel or function.
 
@@ -1596,10 +1594,9 @@ names are reserved for use as access qua
   .. code-block:: c
   kernel void
   foo (read_only image2d_t imageA,
-      write_only image2d_t imageB)
-  {
+      write_only image2d_t imageB) {
   ...
-}
+  }
 
 In the above example imageA is a read-only 2D image object, and imageB is a
 write-only 2D image object.
@@ -1607,8 +1604,7 @@ write-only 2D image object.
 The read_write (or __read_write) qualifier can not be used with pipe.
 
 More details can be found in the OpenCL C language Spec v2.0, Section 6.6.
-    }
-  ];
+    }];
 }
 
 def DocOpenCLAddressSpaces : DocumentationCategory<"OpenCL Address Spaces"> {