Home
last modified time | relevance | path

Searched full:documentation (Results 1 – 25 of 1440) sorted by relevance

12345678910>>...58

/llvm-project/clang/include/clang/StaticAnalyzer/Checkers/
H A DCheckers.td144 Documentation<HasDocumentation>;
151 Documentation<HasDocumentation>,
206 Documentation<HasDocumentation>,
211 Documentation<NotDocumented>,
223 Documentation<HasDocumentation>,
229 Documentation<HasDocumentation>;
233 Documentation<HasDocumentation>;
237 Documentation<HasDocumentation>;
241 Documentation<HasDocumentation>;
245 Documentation<NotDocumente
[all...]
/llvm-project/clang/include/clang/Basic/
H A DAttr.td9 // The documentation is organized by category. Attributes can have category-
10 // specific documentation that is collated within the larger document.
27 currently missing documentation.
32 // in the documentation. This category should be used only when we _want_
38 // documentation. Otherwise, the documentation will specify the attribute has
43 // Specifies the documentation to be associated with the given category.
44 class Documentation {
59 // When set, specifies a label that can be used to reference the documentation.
63 // Specifies that the attribute is explicitly omitted from the documentation,
[all...]
H A DDiagnosticCommentKinds.td10 let CategoryName = "Documentation Issue" in {
17 InGroup<Documentation>, DefaultIgnore;
21 InGroup<Documentation>, DefaultIgnore;
51 InGroup<Documentation>, DefaultIgnore;
55 InGroup<Documentation>, DefaultIgnore;
68 InGroup<Documentation>, DefaultIgnore;
77 InGroup<Documentation>, DefaultIgnore;
84 InGroup<Documentation>, DefaultIgnore;
90 InGroup<Documentation>, DefaultIgnore;
96 InGroup<Documentation>, DefaultIgnore;
[all …]
H A DAttrDocs.td1 //==--- AttrDocs.td - Attribute documentation ----------------------------===//
9 // To test that the documentation builds cleanly, you must run clang-tblgen to
51 def SectionDocs : Documentation {
60 def CodeModelDocs : Documentation {
69 def UsedDocs : Documentation {
90 documentation for further information.
94 def RetainDocs : Documentation {
118 def InitPriorityDocs : Documentation {
155 def InitSegDocs : Documentation {
165 documentation o
[all...]
/llvm-project/clang/include/clang/Tooling/Syntax/
H A DNodes.td21 let documentation = [{
36 let documentation = [{
47 let documentation = [{
58 let documentation = [{
63 let documentation = [{
75 let documentation = [{
83 let documentation = [{
95 let documentation = [{
106 let documentation = [{
114 let documentation = [{
[all …]
/llvm-project/clang/test/Index/
H A Dcomment-cplus11-specific.cpp7 //! This documentation should be inherited.
10 // CHECK: (CXComment_Text Text=[ This documentation should be inherited.])))]
13 //! This is documentation for the typedef (which shows up).
15 // CHECK: (CXComment_Text Text=[ This is documentation for the typedef (which shows up).]))…
17 //! This is documentation for the alias (which shows up).
19 // CHECK: (CXComment_Text Text=[ This is documentation for the alias (which shows up).])))]
22 // CHECK: (CXComment_Text Text=[ This documentation should be inherited.])))]
25 // CHECK: (CXComment_Text Text=[ This documentation should be inherited.])))]
H A Dannotate-comments-typedef.m10 /** Documentation for NSUInteger */
13 /** Documentation for MyEnum */
19 …Documentation for MyEnum </p>] FullCommentAsXML=[<Typedef file="{{[^"]+}}annotate-comments-typedef…
22 /** Documentation for E */
29 …Documentation for E] FullCommentAsHTML=[<p class="para-brief"> Documentation for E </p>] FullComme…
30 …Documentation for E </p>] FullCommentAsXML=[<Typedef file="{{[^"]+}}annotate-comments-typedef.m" l…
/llvm-project/llvm/docs/
H A DREADME.txt1 LLVM Documentation
4 LLVM's documentation is written in reStructuredText, a lightweight
6 reStructuredText documentation should be quite readable in source form, it
7 is mostly meant to be processed by the Sphinx documentation generation
19 The mapping between reStructuredText files and generated documentation is
22 If you are interested in writing new documentation, you will want to read
23 `SphinxQuickstartTemplate.rst` which will get you writing documentation
30 Building the manpages is similar to building the HTML documentation. The
49 The reachability of external links in the documentation can be checked by
H A DSphinxQuickstartTemplate.rst5 …n the state of “I want to write documentation and get it added to LLVM’s docs” and help them start…
13 …documentation is written in `reStructuredText`_, a markup syntax similar to markdown (but much mor…
50 …make your articles task-oriented. You generally should not be writing documentation that isn't bas…
60 this file into a new file for the documentation you are about to write.
168 Generating the documentation
171 You can generate the HTML documentation from the sources locally if you want to
181 Then run cmake to build the documentation inside the ``llvm-project`` checkout:
193 After that you find the generated documentation in ``build/docs/html``
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
196 # documentation from any documented member that it re-implements.
[all …]
/llvm-project/openmp/docs/
H A DREADME.txt1 OpenMP LLVM Documentation
4 OpenMP LLVM's documentation is written in reStructuredText, a lightweight
6 reStructuredText documentation should be quite readable in source form, it
7 is mostly meant to be processed by the Sphinx documentation generation
19 The mapping between reStructuredText files and generated documentation is
23 If you are interested in writing new documentation, you will want to read
25 documentation very fast and includes examples of the most important
31 Building the manpages is similar to building the HTML documentation. The
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
195 # documentation from any documented member that it re-implements.
[all …]
/llvm-project/lldb/docs/
H A Dconf.py3 # LLDB documentation build configuration file, created by
22 # we can generate documentation for its API.
26 # documentation root, use os.path.abspath to make it absolute, like shown here.
35 # Put the generated Python API documentation in the 'python_api' folder. This
41 # If your documentation needs a minimal Sphinx version, state it here.
71 # the Python API documentation.
85 # The theme to use for HTML and HTML Help pages. See the documentation for
117 # The language for content autogenerated by Sphinx. Refer to documentation
130 # Ignore the generated Python documentation that is only used on the website.
160 # The theme to use for HTML and HTML Help pages. See the documentation fo
[all...]
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # This could be handy for archiving the generated documentation or
37 # base path where the generated documentation will be put.
53 # documentation generated by doxygen is written. Doxygen will use this
67 # the file and class documentation (similar to JavaDoc).
98 # inherited members of a class in the documentation of that class as if those
120 # the path mentioned in the documentation of a class, which tells
159 # member inherits the documentation from any documented member that it
165 # a new page for each member. If set to NO, the documentation of a member will
176 # as commands in the documentation. An alias has the form "name=value".
[all …]
/llvm-project/clang-tools-extra/docs/
H A Dindex.rst1 .. title:: Welcome to Extra Clang Tools's documentation!
26 Doxygen Documentation
28 The Doxygen documentation describes the **internal** software that makes up the
30 documentation contains no instructions about how to use the tools, only the APIs
34 * `Doxygen documentation`_
36 .. _`Doxygen documentation`: doxygen/annotated.html
39 This documentation is generated directly from the source code with doxygen.
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
195 # documentation from any documented member that it re-implements.
[all …]
/llvm-project/mlir/test/mlir-pdll-lsp-server/
H A Dsignature-help.test22 // CHECK-NEXT: "documentation": "`op<test.multi>` ODS operand specification",
26 // CHECK-NEXT: "documentation": "64-bit signless integer",
33 // CHECK-NEXT: "documentation": "64-bit signless integer",
42 // CHECK-NEXT: "documentation": "Generic operation operand specification",
46 // CHECK-NEXT: "documentation": "All of the operands of the operation.",
68 // CHECK-NEXT: "documentation": "`op<test.multi>` ODS operand specification",
72 // CHECK-NEXT: "documentation": "64-bit signless integer",
79 // CHECK-NEXT: "documentation": "64-bit signless integer",
101 // CHECK-NEXT: "documentation": "`op<test.multi>` ODS result specification",
105 // CHECK-NEXT: "documentation": "64-bit signless integer",
[all …]
/llvm-project/openmp/runtime/doc/doxygen/
H A Dconfig3 # This file describes the settings to be used by the documentation system
32 # This could be handy for archiving the generated documentation or
44 # included in the documentation. The maximum height of the logo should not
51 # base path where the generated documentation will be put.
67 # documentation generated by doxygen is written. Doxygen will use this
81 # the file and class documentation (similar to JavaDoc).
112 # inherited members of a class in the documentation of that class as if those
136 # the path mentioned in the documentation of a class, which tells
175 # member inherits the documentation from any documented member that it
181 # a new page for each member. If set to NO, the documentation of a member will
[all …]
/llvm-project/bolt/docs/
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
197 # documentation from any documented member that it re-implements.
[all …]
/llvm-project/polly/docs/
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
195 # documentation fro
[all...]
/llvm-project/mlir/docs/
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
196 # documentation from any documented member that it re-implements.
[all …]
/llvm-project/flang/docs/
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
197 # documentation from any documented member that it re-implements.
[all …]
/llvm-project/clang/docs/
H A Ddoxygen.cfg.in3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
195 # documentation from any documented member that it re-implements.
[all …]
/llvm-project/.github/workflows/
H A Drelease-documentation.yml1 name: Release Documentation
14 description: 'Upload documentation'
25 description: 'Upload documentation'
30 release-documentation:
31 name: Build and Upload Release Documentation
55 - name: Build Documentation
89 git commit -a -m "Add ${{ inputs.release-version }} documentation"
/llvm-project/libcxx/docs/
H A DREADME.txt1 libc++ Documentation
4 The libc++ documentation is written using the Sphinx documentation generator. It is
15 The documentation in this directory is published at https://libcxx.llvm.org. It is kept up-to-date
17 documentation is not updating anymore, please contact one of the maintainers.

12345678910>>...58