/netbsd-src/external/apache2/llvm/dist/clang/docs/ |
H A D | ClangFormat.rst | 13 :program:`clang-format` is located in `clang/tools/clang-format` and can be used 14 to format C/C++/Java/JavaScript/Objective-C/Protobuf/C# code. 18 $ clang-format -help 19 OVERVIEW: A tool to format C/C++/Java/JavaScript/Objective-C/Protobuf/C# code. 27 USAGE: clang-format [options] [<file> ...] 31 Clang-format options: 35 =unknown - If set, unknown format options are only warned about. 39 differing format depending on an option being 42 When reading from stdin, clang-format assumes this 45 clang-format from an editor integration [all …]
|
H A D | ClangFormatStyleOptions.rst | 5 :doc:`ClangFormatStyleOptions` describes configurable formatting style options 8 When using :program:`clang-format` command line utility or 9 ``clang::format::reformat(...)`` functions from code, one can either use one of 11 create a custom style by configuring specific style options. 14 Configuring Style with clang-format 17 :program:`clang-format` supports two ways to provide custom style options: 18 directly specify style configuration in the ``-style=`` command line option or 19 use ``-style=file`` and put style configuration in the ``.clang-format`` or 20 ``_clang-format`` file in the project directory. 22 When using ``-style=file``, :program:`clang-format` for each input file will [all …]
|
H A D | LibFormat.rst | 7 as some basic style discussions. 9 If you just want to use `clang-format` as a tool or integrated into an editor, 31 formatting. A list of options can be found under :ref:`style-options`. 33 The style options are described in :doc:`ClangFormatStyleOptions`. 41 The style options describe specific formatting options that can be used in 42 order to make `ClangFormat` comply with different style guides. Currently, 43 several style guides are hard-coded: 47 /// Returns a format style complying with the LLVM coding standards: 51 /// Returns a format style complying with Google's C++ style guide: 55 /// Returns a format style complying with Chromium's style guide: [all …]
|
H A D | ClangTools.rst | 13 directory tree, `clang-tools-extra 14 <https://github.com/llvm/llvm-project/tree/main/clang-tools-extra>`_. 37 common refactoring and rewriting toolkit-style library is also part of 60 ``clang-check`` 68 fixit-hints offered by clang. See :doc:`HowToSetupToolingForLLVM` for 69 instructions on how to setup and used `clang-check`. 71 ``clang-format`` 74 Clang-format is both a :doc:`library <LibFormat>` and a :doc:`stand-alone tool 76 according to configurable style guides. To do so, clang-format uses Clang's 78 the whitespace around those tokens. The goal is for clang-format to serve both [all …]
|
H A D | Tooling.rst | 7 the different ways to write clang tools, and their pros and cons. 12 `LibClang <https://clang.llvm.org/doxygen/group__CINDEX.html>`_ is a stable high 13 level C interface to clang. When in doubt LibClang is probably the interface 24 * want to interface with clang from other languages than C++ 43 * special lint-style warnings or errors for your project 64 tools, as well as integrating into services that run clang tools. Canonical 92 * Syntax checking (:program:`clang-check`) 93 * Automatic fixing of compile errors (:program:`clang-fixit`) 94 * Automatic code formatting (:program:`clang-format`)
|
H A D | UsersManual.rst | 18 `Clang Web Site <https://clang.llvm.org>`_ or the `LLVM Web 25 `Clang Static Analyzer <https://clang-analyzer.llvm.org>`_, please see its web 55 Clang also provides an alternative driver, :ref:`clang-cl`, that is designed 164 output format of the diagnostics that it generates. 235 …<b><span style="color:black">test.c:28:8: <span style="color:magenta">warning</span>: extra tokens… 237 <span style="color:green">^</span> 238 <span style="color:green">//</span> 255 .. option:: -fdiagnostics-format=clang/msvc/vi 257 Changes diagnostic output format to better match IDEs and command line tools. 259 This option controls the output format of the filename, line number, [all …]
|
H A D | LanguageExtensions.rst | 50 #define __has_builtin(x) 0 // Compatibility with non-clang compilers. 85 #define __has_feature(x) 0 // Compatibility with non-clang compilers. 128 name of a double-square-bracket-style attribute. The argument can either be a 145 #if __has_cpp_attribute(clang::fallthrough) 146 #define FALLTHROUGH [[clang::fallthrough]] 152 The attribute scope tokens ``clang`` and ``_Clang`` are interchangeable, as are 170 #define __has_c_attribute(x) 0 // Compatibility with non-clang compilers. 181 The attribute scope tokens ``clang`` and ``_Clang`` are interchangeable, as are 191 a GNU-style attribute. It evaluates to 1 if the attribute is supported by the 197 #define __has_attribute(x) 0 // Compatibility with non-clang compilers. [all …]
|
H A D | OpenCLSupport.rst | 3 <style type="text/css"> 7 </style> 28 For general issues and bugs with OpenCL in clang refer to `Bugzilla 29 <https://bugs.llvm.org/buglist.cgi?component=OpenCL&list_id=172679&product=clang&resolution=--->`__. 67 with regular clang driver they require frontend forwarding, e.g. ``-cc1`` 87 $ clang -cc1 -triple spir64-unknown-unknown -cl-ext=-cl_khr_fp64 test.cl 93 $ clang -cc1 -triple r600-unknown-unknown -cl-ext=-all,+cl_khr_fp16 test.cl 107 $ clang -Xclang -finclude-default-header test.cl 111 to the header location. The header can be found in the clang source tree or 116 $ clang -I<path to clang sources>/lib/Headers/opencl-c.h test.cl [all …]
|
H A D | InternalsManual.rst | 80 ``clang/Basic/Diagnostic*Kinds.td`` files, depending on what library will be 82 diagnostic, the severity of the diagnostic and the English translation + format 129 The format string for the diagnostic is very simple, but it has some power. It 132 some simple format strings: 137 "format string contains '\\0' within the string body" 143 These examples show some important points of format strings. You can use any 156 order as they are specified, you could have a format string with "``%1 %0``" 161 Here are some "best practices" for writing the English format string: 182 including variable names, types, labels, etc. The "``select``" format can be 198 **"s" format** [all …]
|
H A D | ClangCommandLineReference.rst | 3 NOTE: This file is automatically generated by running clang-tblgen 17 GCC-compatible ``clang`` and ``clang++`` drivers. 20 .. program:: clang 35 .. program:: clang 61 .. program:: clang 67 .. program:: clang 85 .. program:: clang 105 Static analyzer report output format (html\|plist\|plist-multi-file\|plist-html\|sarif\|text). 113 .. program:: clang 117 .. program:: clang [all …]
|
/netbsd-src/external/mit/libcbor/dist/ |
H A D | clang-format.sh | 5 if which clang-format-8; then 6 clang-format-8 --verbose -style=file -i **/*.c **/*.h **/*.cpp 8 clang-format --verbose -style=file -i **/*.c **/*.h **/*.cpp
|
H A D | refresh_templates.sh | 4 clang-format -style=file -i $(dirname $0)/test/stream_expectations.c
|
/netbsd-src/external/apache2/llvm/dist/clang/include/clang/Basic/ |
H A D | DiagnosticDocs.td | 12 NOTE: This file is automatically generated by running clang-tblgen 20 <style> 54 </style> 56 .. FIXME: rST doesn't support formatting this, so we format all <td> elements 61 .. Roles generated by clang-tblgen.
|
H A D | DiagnosticGroups.td | 18 // Empty DiagGroups are recognized by clang but ignored. 249 def FormatInsufficientArgs : DiagGroup<"format-insufficient-args">; 250 def FormatExtraArgs : DiagGroup<"format-extra-args">; 251 def FormatZeroLength : DiagGroup<"format-zero-length">; 452 def : DiagGroup<"missing-format-attribute">; 492 def OldStyleCast : DiagGroup<"old-style-cast">; 493 def : DiagGroup<"old-style-definition">; 662 def ObjCCStringFormat : DiagGroup<"cstring-format-directive">; 687 // (#pragma clang optimize, noinline) so suggest nothing for now. 692 def PragmaClangAttribute : DiagGroup<"pragma-clang-attribute">; [all …]
|
/netbsd-src/external/apache2/llvm/dist/clang/cmake/caches/ |
H A D | Apple-stage2.cmake | 1 # This file sets up a CMakeCache for Apple-style stage2 bootstrap. It is 6 set(CLANG_VENDOR_UTI com.apple.clang CACHE STRING "") 12 set(CLANG_LINKS_TO_CREATE clang++ cc c++ CACHE STRING "") 22 set(LLVM_BUILD_EXTERNAL_COMPILER_RT ON CACHE BOOL "Build Compiler-RT with just-built clang") 46 # clang without installing over existing tools. 73 clang 75 clang-format 76 clang-resource-headers
|
/netbsd-src/external/apache2/llvm/dist/llvm/docs/ |
H A D | CoverageMappingFormat.rst | 2 :format: html 14 LLVM's code coverage mapping format is used to provide code coverage 22 documentation <https://clang.llvm.org/docs/SourceBasedCodeCoverage.html>`. 24 We start by briefly describing LLVM's code coverage mapping format and the 25 way that Clang and LLVM's code coverage tool work with this format. After 26 the basics are down, more advanced features of the coverage mapping format 33 LLVM's code coverage mapping format is designed to be a self contained 34 data format that can be embedded into the LLVM IR and into object files. 35 It's described in this document as a **mapping** format because its goal is 42 1. When clang compiles a source file with ``-fcoverage-mapping``, it [all …]
|
H A D | XRay.rst | 57 enabling the ``-fxray-instrument`` flag in your clang invocation. 63 clang -fxray-instrument ... 71 clang -fxray-instrument -fxray-instruction-threshold=1 ... 76 You can do it using the GCC-style attributes or C++11-style attributes. 80 [[clang::xray_always_instrument]] void always_instrumented(); 82 [[clang::xray_never_instrument]] void never_instrumented(); 89 Library`_ or use ``clang`` to link it in automatically with the 92 `libclang_rt.xray-{arch}` where `{arch}` is the mnemonic supported by clang 128 logging from a file. The file's format is described below: 140 These files can be provided through the ``-fxray-attr-list=`` flag to clang. [all …]
|
H A D | GettingStartedVS.rst | 21 The second piece is the `Clang <https://clang.llvm.org/>`_ front end. This 24 machine code. LLVM fully supports the COFF object file format, which is 93 *Note:* some regression tests require Unix-style line ending (``\n``). 188 C:\..> clang -c hello.c -emit-llvm -o hello.bc 196 Alternatively you can directly output an executable with clang with: 200 C:\..> clang hello.c -o hello.exe 202 The ``-o hello.exe`` is required because clang currently outputs ``a.out``
|
/netbsd-src/external/apache2/llvm/dist/llvm/docs/CommandGuide/ |
H A D | llvm-objdump.rst | 66 Display format-specific file headers. 76 .. option:: --raw-clang-ast 78 Dump the raw binary contents of the clang AST section. 126 .. option:: --debug-vars=<format> 129 alongside disassembly. ``format`` may be ``unicode`` or ``ascii``, defaulting 189 Use hex format when printing immediate values in disassembly output. 249 .. option:: --x86-asm-syntax=<style> 252 When used with :option:`--disassemble`, choose style of code to emit from 257 AT&T-style assembly 261 Intel-style assembly [all …]
|
H A D | llvm-cov.rst | 16 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation 190 ``clang`` use the ``-fprofile-instr-generate`` and ``-fcoverage-mapping`` 191 flags. If linking with the ``clang`` driver, pass ``-fprofile-instr-generate`` 198 typically called ``default.profraw``, which can be converted to a format that 267 .. option:: -format=<FORMAT> 269 Use the specified output format. The supported formats are: "text", "html". 274 only supported for the html format. 404 format. 426 .. option:: -format=<FORMAT> 428 Use the specified output format. The supported formats are: "text" (JSON), [all …]
|
/netbsd-src/external/bsd/nvi/usr.bin/nvi/ |
H A D | Makefile | 16 COPTS.exf.c+= -Wno-format-nonliteral 17 COPTS.msg.c+= -Wno-format-nonliteral 19 COPTS.v_increment.c+= -Wno-format-nonliteral 21 CWARNFLAGS.clang+= -Wno-unsequenced 23 CWARNFLAGS.clang+= -Wno-error=string-compare 69 COPTS.regexec.c+= ${${ACTIVE_CC} == "gcc":? -Wno-old-style-definition :}
|
/netbsd-src/external/apache2/llvm/dist/llvm/docs/HistoricalNotes/ |
H A D | 2007-OriginalClangReadme.txt | 8 clang: noun 70 clang - An example driver, client of the libraries at various levels. 88 family must be correctly supported (trigraphs, preprocessor arcana, K&R-style 92 II. Usage of clang driver: 95 - Help: clang --help 127 For more information on getting Graphviz to work with clang/LLVM, 133 * Column numbers are fully tracked (no 256 col limit, no GCC-style pruning). 136 * Full diagnostic customization by client (can format diagnostics however they
|
/netbsd-src/external/apache2/llvm/dist/llvm/docs/Proposals/ |
H A D | VariableNames.rst | 74 but here we use the terminology from clang-tidy). 117 generally encouraged that new code be written in the style of the surrounding 286 1. Add or change the project's .clang-tidy to reflect the agreed rules. 290 2. Apply ``clang-tidy`` to the project's files, with only the 291 ``readability-identifier-naming`` rules enabled. ``clang-tidy`` will also 292 reformat the affected lines according to the rules in ``.clang-format``. 294 clang-tidy, and bugs should be fixed in the process, likely including: 316 * clang-tools-extra 317 * clang 354 .. [WebKit] WebKit Code Style Guidelines https://webkit.org/code-style-guidelines/#names [all …]
|
/netbsd-src/external/apache2/llvm/dist/llvm/tools/llvm-objdump/ |
H A D | ObjdumpOpts.td | 109 def raw_clang_ast : Flag<["--"], "raw-clang-ast">, 110 HelpText<"Dump the raw binary contents of the clang AST section">; 117 HelpText<"Use hex format for immediate values">; 120 HelpText<"Do not use hex format for immediate values (default)">; 124 HelpText<"Display format specific file headers">; 202 HelpText<"Emit AT&T-style disassembly">; 205 HelpText<"Emit Intel-style disassembly">; 211 HelpText<"Display only the first format specific file header">,
|
/netbsd-src/crypto/external/bsd/heimdal/dist/cf/ |
H A D | Makefile.am.common | 146 # It's useful for debugging to format generated sources. The default for all 147 # clang-format styles is to sort includes, but in many cases in-tree we really 154 $(CLANG_FORMAT) -style='{BasedOnStyle: Chromium, SortIncludes: false}' -i $@.tmp.c; \
|