Lines Matching +refs:clang +refs:prefix +refs:header
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
245 .. option:: -fdiagnostics-format=clang/msvc/vi
253 **clang** (default)
529 Disable auto-generation of preprocessed source files during a clang crash.
563 $ clang -O2 -Rpass=inline code.cc -o code
664 by running '``clang --print-diagnostic-categories``'.
692 particularly useful when writing a header file that will be compiled by
701 #pragma clang diagnostic push
702 #pragma clang diagnostic ignored "-Wmultichar"
706 #pragma clang diagnostic pop
746 an included file is treated as a system header if it is found in an
751 being a system header. No warnings will be produced from the location of
758 #pragma clang system_header
762 The :option:`--system-header-prefix=` and :option:`--no-system-header-prefix=`
765 is found within a header search path and starts with a system prefix, the
766 header is treated as a system header. The last prefix on the
767 command-line which matches the specified header name takes precedence.
772 $ clang -Ifoo -isystem bar --system-header-prefix=x/ \
773 --no-system-header-prefix=x/y/
775 Here, ``#include "x/a.h"`` is treated as including a system header, even
776 if the header is found in ``foo``, and ``#include "x/y/b.h"`` is treated
777 as not including a system header, even if the header is found in
781 directory is treated as including a system header if the including file
782 is treated as a system header.
801 `static analyzer <http://clang-analyzer.llvm.org>`_ can also be
803 `annotations <http://clang-analyzer.llvm.org/annotations.html>`_ and the
805 page <http://clang-analyzer.llvm.org/faq.html#exclude_code>`_ for more
816 the same (and often large) header files to be included by multiple
819 headers. Precompiled header files, which represent one of many ways to
822 some of the work needed to process a corresponding header file. While
831 :option:`-x <language>-header` option. This mirrors the interface in GCC
836 $ gcc -x c-header test.h -o test.h.gch
837 $ clang -x c-header test.h -o test.h.pch
842 A PCH file can then be used as a prefix header when a :option:`-include`
843 option is passed to ``clang``:
847 $ clang -include test.h test.c -o test
849 The ``clang`` driver will first check if a PCH file for ``test.h`` is
862 $ clang -x c-header test.h -o test.h.pch
865 $ clang test.c -o test
867 In this example, ``clang`` will not automatically use the PCH file for
874 It is sometimes necessary to build a precompiled header from headers
876 might build a precompiled header within the build tree that is then
882 To build a relocatable precompiled header, place your headers into a
884 if you want to build a precompiled header for the header ``mylib.h``
886 ``build/usr/include`` and place the header ``mylib.h`` into that
891 Building a relocatable precompiled header requires two additional
899 # clang -x c-header --relocatable-pch -isysroot /path/to/build /path/to/build/mylib.h mylib.h.pch
902 PCH file are found from the system header root. For example, ``mylib.h``
911 and the precompiled header cannot be generated after headers have been
1047 performed by ``clang++``, not ``clang``, in order to link against the
1200 $ clang++ -O2 -gline-tables-only code.cc -o code
1242 $ clang++ -O2 -gline-tables-only -fprofile-sample-use=code.prof code.cc -o code
1271 function header specify how many total samples were accumulated in the
1282 defined. So, if the function has its header at line 280, the offset
1347 $ clang++ -O2 -fprofile-instr-generate code.cc -o code
1362 the input expected by clang. Use the ``merge`` command of the llvm-profdata
1377 $ clang++ -O2 -fprofile-instr-use=code.profdata code.cc -o code
1380 profile. As you make changes to your code, clang may no longer be able to
1472 The support for standard C in clang is feature-complete except for the
1475 Extensions supported by clang
1483 clang supports the -std option, which changes what language mode clang
1486 specified, clang defaults to gnu11 mode. Many C99 and C11 features are
1538 clang tries to be compatible with gcc as much as possible, but some gcc
1541 - clang does not support #pragma weak (`bug
1545 - clang does not support decimal floating point types (``_Decimal32`` and
1549 - clang does not support nested functions; this is a complex feature
1562 - clang does not support global register variables; this is unlikely to
1565 - clang does not support static initialization of flexible array
1568 - clang does not support
1572 that because clang pretends to be like GCC 4.2, and this extension
1574 extension with clang at the moment.
1575 - clang does not support the gcc extension for forward-declaring
1591 - clang does not support the gcc extension that allows variable-length
1594 the extension appears to be rarely used. Note that clang *does*
1597 - clang does not have an equivalent to gcc's "fold"; this means that
1598 clang doesn't accept some constructs gcc might accept in contexts
1601 - clang does not support ``__builtin_apply`` and friends; this extension
1609 clang has some experimental support for extensions from Microsoft Visual
1617 clang has a ``-fms-compatibility`` flag that makes clang accept enough
1620 <http://clang.llvm.org/compatibility.html#dep_lookup_bases>`_, which is
1621 a common compatibility issue with clang. This flag is enabled by default
1624 ``-fdelayed-template-parsing`` lets clang delay parsing of function template
1628 - clang allows setting ``_MSC_VER`` with ``-fmsc-version=``. It defaults to
1630 and can greatly affect what Windows SDK and c++stdlib headers clang
1632 - clang does not support the Microsoft extension where anonymous record
1634 - clang supports the Microsoft ``#pragma pack`` feature for controlling
1636 where MSVC and GCC are incompatible clang follows the MSVC
1638 - clang supports the Microsoft ``#pragma comment(lib, "foo.lib")`` feature for
1641 - clang supports the Microsoft ``#pragma comment(linker, "/flag:foo")`` feature
1644 - clang defaults to C++11 for Windows targets.
1651 clang fully implements all of standard C++98 except for exported
1709 For the X86 target, clang supports the :option:`-m16` command line
1736 clang currently contains some support for other architectures (e.g. Sparc);
1740 clang contains limited support for the MSP430 embedded processor, but
1741 both the clang support and the LLVM backend support are highly
1746 platform is quite easy; see ``lib/Basic/Targets.cpp`` in the clang source
1792 - ``GCC versions 4.5.0 to 4.5.3, 4.6.0 to 4.6.2, or 4.7.0 (for the C++ header search path)``
1794 - ``some_directory/bin/clang.exe``
1795 - ``some_directory/bin/clang++.exe``
1815 clang-cl
1818 clang-cl is an alternative command-line interface to Clang driver, designed for
1821 To enable clang-cl to find system headers, libraries, and the linker when run
1826 clang-cl can also be used from inside Visual Studio by using an LLVM Platform
1832 To be compatible with cl.exe, clang-cl supports most of the same command-line
1836 Options that are known to clang-cl, but not currently supported, are ignored
1841 clang-cl.exe: warning: argument unused during compilation: '/Zi'
1845 Options that are not known to clang-cl will cause errors. If they are spelled with a
1850 clang-cl.exe: error: no such file or directory: '/foobar'
1852 Please `file a bug <http://llvm.org/bugs/enter_bug.cgi?product=clang&component=Driver>`_
1853 for any valid cl.exe flags that clang-cl does not understand.
1855 Execute ``clang-cl /?`` to see a list of supported options:
1868 /fallback Fall back to cl.exe if clang-cl fails to compile
1946 -Xclang <arg> Pass <arg> to the clang compiler
1951 When clang-cl is run with the ``/fallback`` option, it will first try to
1956 clang-cl cannot successfully compile all the files. clang-cl may fail to compile