Lines Matching +refs:clang +refs:format +refs:executable
16 `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.
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,
253 **clang** (default)
303 For example, a format string warning will produce these three
342 parsable format after the file/line/column number information. The
362 parseable format at the end of diagnostics. The following example
363 illustrates the format:
529 Disable auto-generation of preprocessed source files during a clang crash.
563 $ clang -O2 -Rpass=inline code.cc -o code
683 by running '``clang --print-diagnostic-categories``'.
723 #pragma clang diagnostic ignored "-Wextra-tokens"
728 #pragma clang diagnostic pop
781 #pragma clang system_header
796 $ clang -Ifoo -isystem bar --system-header-prefix=x/ \
825 `static analyzer <http://clang-analyzer.llvm.org>`_ can also be
827 `annotations <http://clang-analyzer.llvm.org/annotations.html>`_ and the
829 page <http://clang-analyzer.llvm.org/faq.html#exclude_code>`_ for more
861 $ clang -x c-header test.h -o test.h.pch
867 option is passed to ``clang``:
871 $ clang -include test.h test.c -o test
873 The ``clang`` driver will first check if a PCH file for ``test.h`` is
886 $ clang -x c-header test.h -o test.h.pch
889 $ clang test.c -o test
891 In this example, ``clang`` will not automatically use the PCH file for
923 # clang -x c-header --relocatable-pch -isysroot /path/to/build /path/to/build/mylib.h mylib.h.pch
1037 :doc:`SanitizerSpecialCaseList` for file format description.
1232 generated by that tool must then be converted into a format that can be read
1259 $ clang++ -O2 -gline-tables-only code.cc -o code
1261 2. Run the executable under a sampling profiler. The specific profiler
1263 into the format that the LLVM optimizer understands. Currently, there
1277 3. Convert the collected profile data to LLVM's sample profile format.
1301 $ clang++ -O2 -gline-tables-only -fprofile-sample-use=code.prof code.cc -o code
1308 the data generated by the profiler must be converted into a format that can be
1313 information. The format is described below. It can also be generated from
1317 profile files. This is the format generated by the ``create_llvm_prof`` tool
1320 3. GCC encoding. This is based on the gcov format, which is accepted by GCC. It
1329 profiler's native format into one of these three.
1335 This section describes the ASCII text format for sampling profiles. It is,
1469 $ clang++ -O2 -fprofile-instr-generate code.cc -o code
1471 2. Run the instrumented executable with inputs that reflect the typical usage.
1483 3. Combine profiles from multiple runs and convert the "raw" profile format to
1484 the input expected by clang. Use the ``merge`` command of the
1492 since the merge operation also changes the file format.
1499 $ clang++ -O2 -fprofile-instr-use=code.profdata code.cc -o code
1502 profile. As you make changes to your code, clang may no longer be able to
1522 $ clang++ -O2 -fprofile-generate=yyy/zzz code.cc -o code
1664 The support for standard C in clang is feature-complete except for the
1667 Extensions supported by clang
1675 clang supports the -std option, which changes what language mode clang
1678 specified, clang defaults to gnu11 mode. Many C99 and C11 features are
1730 clang tries to be compatible with gcc as much as possible, but some gcc
1733 - clang does not support decimal floating point types (``_Decimal32`` and
1737 - clang does not support nested functions; this is a complex feature
1750 - clang does not support static initialization of flexible array
1753 - clang does not support
1757 that because clang pretends to be like GCC 4.2, and this extension
1759 extension with clang at the moment.
1760 - clang does not support the gcc extension for forward-declaring
1776 - clang does not support the gcc extension that allows variable-length
1779 the extension appears to be rarely used. Note that clang *does*
1782 - clang does not have an equivalent to gcc's "fold"; this means that
1783 clang doesn't accept some constructs gcc might accept in contexts
1786 - clang does not support ``__builtin_apply`` and friends; this extension
1794 clang has support for many extensions from Microsoft Visual C++. To enable these
1800 clang has a ``-fms-compatibility`` flag that makes clang accept enough
1803 <http://clang.llvm.org/compatibility.html#dep_lookup_bases>`_, which is
1804 a common compatibility issue with clang. This flag is enabled by default
1807 ``-fdelayed-template-parsing`` lets clang delay parsing of function template
1811 For compatibility with existing code that compiles with MSVC, clang defines the
1813 and 180000000 respectively, making clang look like an early release of Visual
1816 compatibility version makes clang behave more like that version of MSVC. For
1825 clang fully implements all of standard C++98 except for exported
1909 For the X86 target, clang supports the :option:`-m16` command line
1936 clang currently contains some support for other architectures (e.g. Sparc);
1940 clang contains limited support for the MSP430 embedded processor, but
1941 both the clang support and the LLVM backend support are highly
1946 platform is quite easy; see ``lib/Basic/Targets.cpp`` in the clang source
1994 - ``some_directory/bin/clang.exe``
1995 - ``some_directory/bin/clang++.exe``
2007 Clang expects the GCC executable "gcc.exe" compiled for
2015 clang-cl
2018 clang-cl is an alternative command-line interface to Clang driver, designed for
2021 To enable clang-cl to find system headers, libraries, and the linker when run
2026 clang-cl can also be used from inside Visual Studio by using an LLVM Platform
2032 To be compatible with cl.exe, clang-cl supports most of the same command-line
2036 Options that are known to clang-cl, but not currently supported, are ignored
2041 clang-cl.exe: warning: argument unused during compilation: '/AI'
2045 Options that are not known to clang-cl will be ignored by default. Use the
2051 clang-cl.exe: error: no such file or directory: '/foobar'
2053 Please `file a bug <http://llvm.org/bugs/enter_bug.cgi?product=clang&component=Driver>`_
2054 for any valid cl.exe flags that clang-cl does not understand.
2056 Execute ``clang-cl /?`` to see a list of supported options:
2071 /fallback Fall back to cl.exe if clang-cl fails to compile
2074 /Fe<file or directory> Set output executable file or directory (ends in / or \)
2083 /GA Assume thread-local variables are defined in the executable
2186 -Xclang <arg> Pass <arg> to the clang compiler
2191 When clang-cl is run with the ``/fallback`` option, it will first try to
2196 clang-cl cannot successfully compile all the files. clang-cl may fail to compile