From: Aaron Ballman Date: Fri, 26 Feb 2016 13:30:58 +0000 (+0000) Subject: Giving this attribute documentation group a heading; fixes a documentation generation... X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f3a87677e1a70e1ae7ea38019ee850e839e11218;p=clang Giving this attribute documentation group a heading; fixes a documentation generation error. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@262012 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/include/clang/Basic/AttrDocs.td b/include/clang/Basic/AttrDocs.td index f1a6ae2b1c..080f555a74 100644 --- a/include/clang/Basic/AttrDocs.td +++ b/include/clang/Basic/AttrDocs.td @@ -1583,7 +1583,10 @@ s6.11.5 for details. def OpenCLAccessDocs : Documentation { let Category = DocCatStmt; - 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,7 +1599,7 @@ names are reserved for use as access qualifiers and shall not be used otherwise. 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. @@ -1604,7 +1607,8 @@ 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"> {