Home
last modified time | relevance | path

Searched +refs:clang +refs:format +refs:style (Results 1 – 25 of 31) sorted by relevance

12

/minix3/external/bsd/llvm/dist/clang/docs/
H A DClangFormat.rst13 :program:`clang-format` is located in `clang/tools/clang-format` and can be used
14 to format C/C++/Obj-C code.
18 $ clang-format -help
19 OVERVIEW: A tool to format C/C++/Obj-C code.
27 USAGE: clang-format [options] [<file> ...]
31 Clang-format options:
34 clang-format from an editor integration
36 Can be used with -style option.
42 -length, clang-format will format up to the end
45 -lines=<string> - <start line>:<end line> - format a range of
[all …]
H A DClangFormatStyleOptions.rst5 :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 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 DLibFormat.rst7 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`.
39 The style options describe specific formatting options that can be used in
40 order to make `ClangFormat` comply with different style guides. Currently,
41 two style guides are hard-coded:
45 /// \brief Returns a format style complying with the LLVM coding standards:
49 /// \brief Returns a format style complying with Google's C++ style guide:
54 through the `-style` option.
H A DClangTools.rst21 - ``cd llvm/tools/clang/tools``
22 - ``svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk extra``
26 - ``cd llvm/tools/clang/tools``
27 - ``git clone http://llvm.org/git/clang-tools-extra.git extra``
50 common refactoring and rewriting toolkit-style library is also part of
73 ``clang-check``
81 fixit-hints offered by clang. See :doc:`HowToSetupToolingForLLVM` for
82 instructions on how to setup and used `clang-check`.
84 ``clang-format``
87 Clang-format is both a :doc:`library <LibFormat>` and a :doc:`stand-alone tool
[all …]
H A DTooling.rst7 the different ways to write clang tools, and their pros and cons.
12 `LibClang <http://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 DUsersManual.rst16 `Clang Web Site <http://clang.llvm.org>`_ or the `LLVM Web
23 `Clang Static Analyzer <http://clang-analyzer.llvm.org>`_, please see its web
47 Clang also provides an alternative driver, :ref:`clang-cl`, that is designed
154 output format of the diagnostics that it generates.
225 …<b><span style="color:black">test.c:28:8: <span style="color:magenta">warning</span>: extra tokens…
227 <span style="color:green">^</span>
228 <span style="color:green">//</span>
245 .. option:: -fdiagnostics-format=clang/msvc/vi
247 Changes diagnostic output format to better match IDEs and command line tools.
249 This option controls the output format of the filename, line number,
[all …]
H A DReleaseNotes.rst25 Site <http://clang.llvm.org>`_ or the `LLVM Web
41 queries GNU-style attributes. With the addition of __has_cpp_attribute and
45 - clang-format now supports formatting Java code.
103 may also be expressed using the `#pragma clang loop` directive. See the Clang
105 <http://clang.llvm.org/docs/LanguageExtensions.html#extensions-for-loop-hint-optimizations>`_
188 `the C++ status page <http://clang.llvm.org/cxx_status.html>`_.
196 `status <https://github.com/clang-omp/clang/wiki/Status-of-supported-OpenMP-constructs>_`.
209 page <http://clang.llvm.org/>`_. The web page contains versions of the
212 this release by going into the "``clang/docs/``" directory in the Clang
H A DAttributeReference.rst3 NOTE: This file is automatically generated by running clang-tblgen
29 Clang supports the GNU style ``__attribute__((interrupt("TYPE")))`` attribute on
66 acquire_capability (acquire_shared_capability, clang::acquire_capability, clang::acquire_shared_cap…
76 assert_capability (assert_shared_capability, clang::assert_capability, clang::assert_shared_capabil…
241 a future version of clang. Also, the ABI is not standardized and the name
332 format (gnu::format)
339 Clang supports the ``format`` attribute, which indicates that the function
340 accepts a ``printf`` or ``scanf``-like format string and corresponding
343 Please see `GCC documentation about format attribute
349 #. Clang checks that the function with the ``format`` attribute is called with
[all …]
H A DInternalsManual.rst80 ``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 Ddoxygen.cfg.in7 # The format is:
20 PROJECT_NAME = clang
37 # format and will distribute the generated files over these directories.
61 # whereas setting the tag to NO uses a Unix-style encoding (the default for
136 # will interpret the first line (until the first dot) of a JavaDoc-style
138 # comments will behave just like the Qt-style comments (thus requiring an
429 # The WARN_FORMAT tag determines the format of the warning messages that
432 # warning originated and the warning text. Optionally the format may contain
612 IGNORE_PREFIX = clang::
648 # style sheet that is used by each HTML page. It can be used to
[all …]
H A DModules.rst99 … the full complexity of the language. Maintaining a stable binary module format across architectur…
347 …qualifier specifies that this module corresponds to a Darwin-style framework. A Darwin-style frame…
657 …fying "clangBasic" would instruct the linker to link with ``-lclangBasic`` for a Unix-style linker.
665 format and the linker. The notion is similar to Microsoft Visual
750 … in the grammar to describe specific behavior of other declarations. The format of attributes is f…
846 To detect and help address some of these problems, the ``clang-tools-extra`` repository contains a …
865 ``clang/lib/Headers/module.modulemap``
868 ``clang/test/Modules/``
871 ``clang/include/clang/Basic/Module.h``
874 ``clang/include/clang/Lex/ModuleMap.h``
[all …]
/minix3/external/bsd/llvm/dist/llvm/docs/
H A DCoverageMappingFormat.rst2 :format: html
14 LLVM's code coverage mapping format is used to provide code coverage
24 then we briefly desribe 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
40 ``clang -o test -fprofile-instr-generate -fcoverage-mapping test.c``
56 LLVM's code coverage mapping format is designed to be a self contained
57 data format, that can be embedded into the LLVM IR and object files.
58 It's described in this document as a **mapping** format because its goal is
65 1. When clang compiles a source file with ``-fcoverage-mapping``, it
[all …]
H A DCodingStandards.rst24 use the style that is already being used so that the source is uniform and
93 * Clang: http://clang.llvm.org/cxx_status.html
239 A few things to note about this particular format: The "``-*- C++ -*-``" string
284 In general, prefer C++ style (``//``) comments. They take less space, require
286 useful to use C style (``/* */``) comments however:
288 #. When writing C code: Obviously if you are writing C code, use C style
293 #. When writing a source file that is used by a tool that only accepts C style
297 properly and are better behaved in general than C style comments.
480 As always, follow the `Golden Rule`_ above: follow the style of
498 When formatting a multi-line lambda, format it like a block of code, that's
[all …]
H A DDeveloperPolicy.rst93 different tool, make sure it uses the ``diff -u`` format and that it
222 Note that llvm/test and clang/test are designed for regression and small feature
385 To address these problems, LLVM uses an incremental development style and we
442 When the IR format has to be changed, keep in mind that we try to maintain some
446 * The textual format is not backwards compatible. We don't change it too often,
449 * The bitcode format produced by a X.Y release will be readable by all following
496 contradicts the license (which is a liberal BSD-style license), and that the
/minix3/share/mk/
H A Dbsd.sys.mk19 .if exists(/usr/pkg/bin/clang) || exists(/usr/bin/clang)
20 CC?= clang
79 CXXFLAGS+= -Wold-style-cast
86 CFLAGS+= -Wold-style-definition
92 CFLAGS+= ${${ACTIVE_CC} == "gcc":? -Wno-format-zero-length :}
H A Dsys.mk32 .if exists(/usr/pkg/bin/clang) || exists(/usr/bin/clang)
33 CC?= clang
85 …N-Wno-pointer-sign:N-ffreestanding:N-std=gnu[0-9][0-9]:N-Wold-style-definition:N-Wno-format-zero-l…
/minix3/external/bsd/llvm/dist/llvm/docs/HistoricalNotes/
H A D2007-OriginalClangReadme.txt8 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
/minix3/external/bsd/llvm/dist/clang/include/clang/Basic/
H A DDiagnosticGroups.td19 // Empty DiagGroups are recognized by clang but ignored.
118 def FormatExtraArgs : DiagGroup<"format-extra-args">;
119 def FormatZeroLength : DiagGroup<"format-zero-length">;
227 def : DiagGroup<"missing-format-attribute">;
252 def OldStyleCast : DiagGroup<"old-style-cast">;
253 def : DiagGroup<"old-style-definition">;
363 def ObjCCStringFormat : DiagGroup<"cstring-format-directive">;
453 def VectorConversion : DiagGroup<"vector-conversion">; // clang specific
549 def FormatInvalidSpecifier : DiagGroup<"format-invalid-specifier">;
550 def FormatSecurity : DiagGroup<"format-security">;
[all …]
H A DAttrDocs.td13 NOTE: This file is automatically generated by running clang-tblgen
124 …let Heading = "assert_capability (assert_shared_capability, clang::assert_capability, clang::asser…
133 …let Heading = "acquire_capability (acquire_shared_capability, clang::acquire_capability, clang::ac…
141 …= "try_acquire_capability (try_acquire_shared_capability, clang::try_acquire_capability, clang::tr…
152 …let Heading = "release_capability (release_shared_capability, clang::release_capability, clang::re…
387 // void nodupfunc() [[clang::noduplicate]];
591 The ``clang::fallthrough`` attribute is used along with the
614 [[clang::fallthrough]];
622 [[clang::fallthrough]];
626 [[clang::fallthrough]]; // warning: fallthrough annotation does not
[all …]
/minix3/external/bsd/tcpdump/dist/
H A Daclocal.m481 dnl that defines __GNUC__, which means clang, for example, counts as "gcc".
121 # This is assumed either to be GCC or clang, both
132 # +We, and doesn't handle GCC-style -W flags, so we
133 # don't want to try using GCC-style -W flags.
143 # so, and doesn't handle GCC-style -W flags, so we
144 # don't want to try using GCC-style -W flags.
179 # so, and doesn't handle GCC-style -W flags, so we
180 # don't want to try using GCC-style -W flags.
247 dnl Makefile-style dependency lines
286 # MIPS C for IRIX, DEC C, and clang all use -M.
[all …]
/minix3/external/bsd/libpcap/dist/
H A Daclocal.m481 dnl that defines __GNUC__, which means clang, for example, counts as "gcc".
113 # This is assumed either to be GCC or clang, both
124 # +We, and doesn't handle GCC-style -W flags, so we
125 # don't want to try using GCC-style -W flags.
135 # so, and doesn't handle GCC-style -W flags, so we
136 # don't want to try using GCC-style -W flags.
171 # so, and doesn't handle GCC-style -W flags, so we
172 # don't want to try using GCC-style -W flags.
231 # We're assuming this is clang, where
269 dnl Makefile-style dependency lines
[all …]
/minix3/minix/lib/liblwip/dist/doc/doxygen/
H A Dlwip.Doxyfile10 # The format is:
64 # directories (in 2 levels) under the output directory of each output format and
184 # first line (until the first dot) of a Javadoc-style comment as the brief
185 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
186 # style comments (thus requiring an explicit @brief command for a brief
193 # line (until the first dot) of a Qt-style comment as the brief description. If
194 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
280 # using this tag. The format is ext=language, where ext is a file extension, and
282 # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
297 # according to the Markdown format, which allows for more readable
[all …]
/minix3/external/bsd/llvm/dist/clang/docs/tools/
H A Dclang.pod5 clang - the Clang C, C++, and Objective-C compiler
9 B<clang> [B<-c>|B<-S>|B<-E>] B<-std=>I<standard> B<-g>
22 B<clang> is a C, C++, and Objective-C compiler which encompasses preprocessing,
32 The B<clang> executable is actually a small driver which controls the overall
84 same driver. Please see L<http://clang-analyzer.llvm.org> for more details
169 Enable support for Pascal-style strings with "\pfoo".
364 otherwise this generates LLVM bitcode format object files (which may be passed
526 Do not search clang's builtin directory for include files.
612 Maintained by the Clang / LLVM Team (L<http://clang.llvm.org>).
/minix3/external/bsd/llvm/dist/clang/include/clang/Driver/
H A DCC1Options.td1 //===--- CC1Options.td - Options for clang -cc1 ---------------------------===//
10 // This file defines the options accepted by clang -cc1 and clang -cc1as.
163 HelpText<"Emit newer GNU style pubnames">;
254 HelpText<"Print cl.exe style /showIncludes to stdout">;
264 HelpText<"File for serializing diagnostics in a binary format">;
266 def fdiagnostics_format : Separate<["-"], "fdiagnostics-format">,
444 HelpText<"Use SjLj style exceptions">;
H A DOptions.td1 //===--- Options.td - Options for clang -----------------------------------===//
10 // This file defines the options accepted by clang.
37 // clang and clang-cl modes.
44 // CC1Option - This option should be accepted by clang -cc1.
47 // CC1AsOption - This option should be accepted by clang -cc1as.
72 def f_clang_Group : OptionGroup<"<f (clang-only) group>">, Group<CompileOnly_Group>;
76 def clang_i_Group : OptionGroup<"<clang i group>">, Group<i_Group>;
90 // Temporary groups for clang options which we know we don't support,
92 def clang_ignored_f_Group : OptionGroup<"<clang ignored f group>">,
94 def clang_ignored_m_Group : OptionGroup<"<clang ignored m group>">,
[all …]

12