Lines Matching +refs:clang +refs:format +refs:binary

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
348 …exprs.c:47:15:{47:8-47:14}{47:17-47:24}: error: invalid operands to binary expression ('int *' and…
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
669 by running '``clang   --print-diagnostic-categories``'.
706   #pragma clang diagnostic push
707   #pragma clang diagnostic ignored "-Wmultichar"
711   #pragma clang diagnostic pop
763   #pragma clang system_header
777   $ clang -Ifoo -isystem bar --system-header-prefix=x/ \
806 `static analyzer <http://clang-analyzer.llvm.org>`_ can also be
808 `annotations <http://clang-analyzer.llvm.org/annotations.html>`_ and the
810 page <http://clang-analyzer.llvm.org/faq.html#exclude_code>`_ for more
842   $ clang -x c-header test.h -o test.h.pch
848 option is passed to ``clang``:
852   $ clang -include test.h test.c -o test
854 The ``clang`` driver will first check if a PCH file for ``test.h`` is
867     $ clang -x c-header test.h -o test.h.pch
870     $ clang test.c -o test
872   In this example, ``clang`` will not automatically use the PCH file for
904   # clang -x c-header --relocatable-pch -isysroot /path/to/build /path/to/build/mylib.h mylib.h.pch
1017       :doc:`SanitizerSpecialCaseList` for file format description.
1052    performed by ``clang++``, not ``clang``, in order to link against the
1163      $ clang++ -O2 -gline-tables-only code.cc -o code
1167    into the format that the LLVM optimizer understands. Currently, there
1181 3. Convert the collected profile data to LLVM's sample profile format.
1189      $ create_llvm_prof --binary=./code --out=code.prof
1191    This will read ``perf.data`` and the binary file ``./code`` and emit
1197    the profile back to the optimizers. This should result in a binary
1205      $ clang++ -O2 -gline-tables-only -fprofile-sample-use=code.prof code.cc -o code
1212 write a conversion tool from your profiler to LLVM's format. This section
1213 explains the file format expected by the backend.
1217 section has the following format (taken from
1310      $ clang++ -O2 -fprofile-instr-generate code.cc -o code
1324 3. Combine profiles from multiple runs and convert the "raw" profile format to
1325    the input expected by clang. Use the ``merge`` command of the llvm-profdata
1333    since the merge operation also changes the file format.
1340      $ clang++ -O2 -fprofile-instr-use=code.profdata code.cc -o code
1343    profile. As you make changes to your code, clang may no longer be able to
1369   information in the binary. They work based on the assumption that
1435 The support for standard C in clang is feature-complete except for the
1438 Extensions supported by clang
1446 clang supports the -std option, which changes what language mode clang
1448 various aliases for those modes. If no -std option is specified, clang
1493 clang tries to be compatible with gcc as much as possible, but some gcc
1496 -  clang does not support #pragma weak (`bug
1500 -  clang does not support decimal floating point types (``_Decimal32`` and
1504 -  clang does not support nested functions; this is a complex feature
1517 -  clang does not support global register variables; this is unlikely to
1520 -  clang does not support static initialization of flexible array
1523 -  clang does not support
1527    that because clang pretends to be like GCC 4.2, and this extension
1529    extension with clang at the moment.
1530 -  clang does not support the gcc extension for forward-declaring
1546 -  clang does not support the gcc extension that allows variable-length
1549    the extension appears to be rarely used. Note that clang *does*
1552 -  clang does not have an equivalent to gcc's "fold"; this means that
1553    clang doesn't accept some constructs gcc might accept in contexts
1556 -  clang does not support ``__builtin_apply`` and friends; this extension
1564 clang has some experimental support for extensions from Microsoft Visual
1572 clang has a ``-fms-compatibility`` flag that makes clang accept enough
1575 <http://clang.llvm.org/compatibility.html#dep_lookup_bases>`_, which is
1576 a common compatibility issue with clang. This flag is enabled by default
1579 ``-fdelayed-template-parsing`` lets clang delay parsing of function template
1583 -  clang allows setting ``_MSC_VER`` with ``-fmsc-version=``. It defaults to
1585    and can greatly affect what Windows SDK and c++stdlib headers clang
1587 -  clang does not support the Microsoft extension where anonymous record
1589 -  clang supports the Microsoft ``#pragma pack`` feature for controlling
1591    where MSVC and GCC are incompatible clang follows the MSVC
1593 -  clang supports the Microsoft ``#pragma comment(lib, "foo.lib")`` feature for
1596 -  clang supports the Microsoft ``#pragma comment(linker, "/flag:foo")`` feature
1599 -  clang defaults to C++11 for Windows targets.
1606 clang fully implements all of standard C++98 except for exported
1664 For the X86 target, clang supports the :option:`-m16` command line
1691 clang currently contains some support for other architectures (e.g. Sparc);
1695 clang contains limited support for the MSP430 embedded processor, but
1696 both the clang support and the LLVM backend support are highly
1701 platform is quite easy; see ``lib/Basic/Targets.cpp`` in the clang source
1749 -  ``some_directory/bin/clang.exe``
1750 -  ``some_directory/bin/clang++.exe``
1770 clang-cl
1773 clang-cl is an alternative command-line interface to Clang driver, designed for
1776 To enable clang-cl to find system headers, libraries, and the linker when run
1781 clang-cl can also be used from inside Visual Studio  by using an LLVM Platform
1787 To be compatible with cl.exe, clang-cl supports most of the same command-line
1791 Options that are known to clang-cl, but not currently supported, are ignored
1796     clang-cl.exe: warning: argument unused during compilation: '/Zi'
1800 Options that are not known to clang-cl will cause errors. If they are spelled with a
1805     clang-cl.exe: error: no such file or directory: '/foobar'
1807 Please `file a bug <http://llvm.org/bugs/enter_bug.cgi?product=clang&component=Driver>`_
1808 for any valid cl.exe flags that clang-cl does not understand.
1810 Execute ``clang-cl /?`` to see a list of supported options:
1817     /fallback              Fall back to cl.exe if clang-cl fails to compile
1867 When clang-cl is run with the ``/fallback`` option, it will first try to
1872 clang-cl cannot successfully compile all the files. clang-cl may fail to compile