$ clang-format --help

OVERVIEW: A tool to format C/C++/Obj-C code.

If no arguments are specified, it formats the code from standard input

and writes the result to the standard output.

If <file> is given, it reformats the file. If -i is specified together

or save any files. To revert a formatting, just undo.

Script for patch reformatting

=============================

optional arguments:

-h, --help show this help message and exit

-p P strip the smallest prefix containing P slashes

So to reformat all the lines in the latest :program:`git` commit, just do:

* convert loops to range-based for loops;

Extra Clang Tools

=================

``foo.begin()`` into ``begin(foo)`` and similarly for ``end()``, where

``foo`` is a standard container. We could also detect similar patterns for

arrays.

* ``tr1`` removal tool. Will migrate source code from using TR1 library

features to C++11 library. For example:

that don't want to use ``auto`` because they are afraid that they might lose

control over their code.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Use ``__has_feature(cxx_inheriting_constructors)`` to determine if support for

C++11 inline namespaces

^^^^^^^^^^^^^^^^^^^^^^^

``__has_extension(cxx_static_assert)`` to determine if support for compile-time

assertions using ``static_assert`` is enabled.

C++11 type inference

^^^^^^^^^^^^^^^^^^^^

``__has_extension(cxx_variadic_templates)`` to determine if support for

variadic templates is enabled.

C11

---

to determine if support for compile-time assertions using ``_Static_assert`` is

enabled.

Checks for Type Traits

======================

</pre></td></tr>

<tr><td>Matcher&lt<a href="http://clang.llvm.org/doxygen/classclang_1_1CXXOperatorCallExpr.html">CXXOperatorCallExpr</a>&gt;</td><td class="name" onclick="toggle('hasOverloadedOperatorName1')"><a name="hasOverloadedOperatorName1Anchor">hasOverloadedOperatorName</a></td><td>StringRef Name</td></tr>

<tr><td colspan="4" class="doc" id="hasOverloadedOperatorName1"><pre>Matches overloaded operator names.

git clone http://llvm.org/git/llvm.git

cd llvm/tools

git clone http://llvm.org/git/clang.git

Next you need to obtain the CMake build system and Ninja build tool. You

may already have CMake installed, but current binary versions of CMake

.. code-block:: console

bin/loop-convert test.cpp --

Note the two dashes after we specify the source file. The additional

class LoopPrinter : public MatchFinder::MatchCallback {

public :

virtual void run(const MatchFinder::MatchResult &Result) {

};

And change ``main()`` to:

(IntegerLiteral 0x173afa8 'int' 0)")

<<>>

(BinaryOperator 0x173b060 '_Bool' '<'

(DeclRefExpr 0x173afe0 'int' lvalue Var 0x173af50 'i' 'int'))

(DeclRefExpr 0x173b008 'const int' lvalue Var 0x170fa80 'N' 'const int')))

(UnaryOperator 0x173b0b0 'int' lvalue prefix '++'

(DeclRefExpr 0x173b088 'int' lvalue Var 0x173af50 'i' 'int'))

We already know that the declaration and increments both match, or this

loop wouldn't have been dumped. The culprit lies in the implicit cast

InitVarName, and IncrementVarName), we can obtain the matched nodes by

using the ``getNodeAs()`` member function.

.. code-block:: c++

#include "clang/AST/ASTContext.h"

void LoopPrinter::run(const MatchFinder::MatchResult &Result) {

ASTContext *Context = Result.Context;

// We do not want to convert header files!

if (!FS || !Context->getSourceManager().isFromMainFile(FS->getForLoc()))

return;

.. code-block:: c++

If execution reaches the end of ``LoopPrinter::run()``, we know that the

loop shell that looks like

The next section will deal with recursively traversing the AST to

discover all changes needed.

canonicalize expressions:

.. code-block:: c++

return 0;

}

If a bug is detected, the program will print an error message to

stderr and exit with a non-zero exit code. Currently, MemorySanitizer

.. code-block:: console

% ./a.out 2>log

% projects/compiler-rt/lib/asan/scripts/asan_symbolize.py / < log | c++filt

==14425== WARNING: MemorySanitizer: UMR (uninitialized-memory-read)

address space. This means that tools like ``ulimit`` may not work as

usually expected.

* Static linking is not supported.

* Depending on the version of Linux kernel, running without ASLR may

be not supported. Note that GDB disables ASLR by default. To debug

instrumented programs, use "set disable-randomization off".

``-fmodules-cache-path=<directory>``

Specify the path to the modules cache. If not provided, Clang will select a system-appropriate default.

``-fmodules-ignore-macro=macroname``

Instruct modules to ignore the named macro when selecting an appropriate module variant. Use this for macros defined on the command line that don't affect how modules are built, to improve sharing of compiled module files.

.. contents::

:local:

Written by the `LLVM Team <http://llvm.org/>`_

Introduction

============

This document contains the release notes for the Clang C/C++/Objective-C

frontend, part of the LLVM Compiler Infrastructure, release 3.3. Here we

What's New in Clang 3.3?

========================

Some of the major new features and improvements to Clang are listed

here. Generic improvements to Clang as a whole or to its underlying

Major New Features

------------------

explain them more clearly, and provide more accurate source information

about them. The improvements since the 3.2 release include:

Extended Identifiers: Unicode Support and Universal Character Names

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

directly in the source file using the UTF-8 encoding, or referred to using

*universal character names* (``\u00E0``, ``\U000000E0``).

C Language Changes in Clang

---------------------------

C++ Language Changes in Clang

-----------------------------

Internal API Changes

--------------------

For each variable and function Clang used to keep the storage class as written

in the source, the linkage and a semantic storage class. This was a bit

redundant and the semantic storage class has been removed. The method

Significant Known Problems

==========================

Additional Information

======================

Usage

-----

Example:

return Global;

}

If a bug is detected, the program will print an error message to stderr.

Currently, ThreadSanitizer symbolizes its output using an external

* ThreadSanitizer maps (but does not reserve) a lot of virtual address space.

This means that tools like ``ulimit`` may not work as usually expected.

* Libc/libstdc++ static linking is not supported.

Current Status

--------------

of warnings, so even when using GCC compatible #pragmas there is no

guarantee that they will have identical behaviour on both compilers.

Controlling Diagnostics in System Headers

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Generate complete debug info.

.. _c:

C Language Features

=head1 SYNOPSIS

B<clang> [B<-c>|B<-S>|B<-E>] B<-std=>I<standard> B<-g>

B<-W>I<warnings...> B<-pedantic>

B<-I>I<dir...> B<-L>I<dir...>

B<-D>I<macro[=defn]>

=over

Specify which optimization level to use. B<-O0> means "no optimization": this

level compiles the fastest and generates the most debuggable code. B<-O2> is a

B<-O2> with extra optimizations to reduce code size. B<-Oz> is like B<-Os>

(and thus B<-O2>), but reduces code size further. B<-O3> is like B<-O2>,

except that it enables optimizations that take longer to perform or that may

supported platforms, B<-O4> enables link-time optimization; object files are

stored in the LLVM bitcode file format and whole program optimization is done at

link time. B<-O1> is somewhere between B<-O0> and B<-O2>.