diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/BlockImplementation.txt | 2 | ||||
| -rw-r--r-- | docs/LanguageExtensions.html | 22 | ||||
| -rw-r--r-- | docs/PCHInternals.html | 14 | ||||
| -rw-r--r-- | docs/PTHInternals.html | 22 | ||||
| -rw-r--r-- | docs/UsersManual.html | 24 | ||||
| -rw-r--r-- | docs/libIndex.html | 4 |
6 files changed, 67 insertions, 21 deletions
diff --git a/docs/BlockImplementation.txt b/docs/BlockImplementation.txt index b2ad405..c420455 100644 --- a/docs/BlockImplementation.txt +++ b/docs/BlockImplementation.txt @@ -292,7 +292,7 @@ would be rewritten to be: int flags; //refcount; int size; int captured_i; - } i = { NULL, &i, 0, sizeof(struct _block_byref_i), 11; + } i = { NULL, &i, 0, sizeof(struct _block_byref_i), 11 }; i.forwarding->captured_i = 11; diff --git a/docs/LanguageExtensions.html b/docs/LanguageExtensions.html index 1c892fd..414d9c8 100644 --- a/docs/LanguageExtensions.html +++ b/docs/LanguageExtensions.html @@ -23,6 +23,11 @@ td { <li><a href="#has_include">Include File Checking Macros</a></li> <li><a href="#builtinmacros">Builtin Macros</a></li> <li><a href="#vectors">Vectors and Extended Vectors</a></li> +<li><a href="#checking_language_features">Checks for Standard Language Features</a></li> + <ul> + <li><a href="#cxx_exceptions">C++ exceptions</a></li> + <li><a href="#cxx_rtti">C++ RTTI</a></li> + </ul> <li><a href="#blocks">Blocks</a></li> <li><a href="#overloading-in-c">Function Overloading in C</a></li> <li><a href="#builtins">Builtin Functions</a> @@ -194,6 +199,23 @@ href="#__builtin_shufflevector">__builtin_shufflevector</a>.</p> <p>Query for this feature with __has_feature(attribute_ext_vector_type).</p> <!-- ======================================================================= --> +<h2 id="checking_language_features">Checks for Standard Language Features</h2> +<!-- ======================================================================= --> + +<p>The <tt>__has_feature</tt> macro can be used to query if certain standard language features are +enabled. Those features are listed here.</p> + +<h3 id="cxx_exceptions">C++ exceptions</h3> + +<p>Use <tt>__has_feature(cxx_exceptions)</tt> to determine if C++ exceptions have been enabled. For +example, compiling code with <tt>-fexceptions</tt> enables C++ exceptions.</p> + +<h3 id="cxx_rtti">C++ RTTI</h3> + +<p>Use <tt>__has_feature(cxx_rtti)</tt> to determine if C++ RTTI has been enabled. For example, +compiling code with <tt>-fno-rtti</tt> disables the use of RTTI.</p> + +<!-- ======================================================================= --> <h2 id="blocks">Blocks</h2> <!-- ======================================================================= --> diff --git a/docs/PCHInternals.html b/docs/PCHInternals.html index b34b6a2..e21ec5e 100644 --- a/docs/PCHInternals.html +++ b/docs/PCHInternals.html @@ -26,7 +26,7 @@ <p><b>Table of Contents</b></p> <ul> <li><a href="#usage">Using Precompiled Headers with - <tt>clang-cc</tt></a></li> + <tt>clang</tt></a></li> <li><a href="#philosophy">Design Philosophy</a></li> <li><a href="#contents">Precompiled Header Contents</a> <ul> @@ -44,15 +44,15 @@ Points</a></li> </ul> -<h2 id="usage">Using Precompiled Headers with <tt>clang-cc</tt></h2> +<h2 id="usage">Using Precompiled Headers with <tt>clang</tt></h2> -<p>The low-level Clang compiler, <tt>clang-cc</tt>, supports two command -line options for generating and using PCH files.<p> +<p>The Clang compiler frontend, <tt>clang -cc1</tt>, supports two command line +options for generating and using PCH files.<p> -<p>To generate PCH files using <tt>clang-cc</tt>, use the option +<p>To generate PCH files using <tt>clang -cc1</tt>, use the option <b><tt>-emit-pch</tt></b>: -<pre> $ clang-cc test.h -emit-pch -o test.h.pch </pre> +<pre> $ clang -cc1 test.h -emit-pch -o test.h.pch </pre> <p>This option is transparently used by <tt>clang</tt> when generating PCH files. The resulting PCH file contains the serialized form of the @@ -61,7 +61,7 @@ semantic analysis. The PCH file can then be used as a prefix header with the <b><tt>-include-pch</tt></b> option:</p> <pre> - $ clang-cc -include-pch test.h.pch test.c -o test.s + $ clang -cc1 -include-pch test.h.pch test.c -o test.s </pre> <h2 id="philosophy">Design Philosophy</h2> diff --git a/docs/PTHInternals.html b/docs/PTHInternals.html index 832d3b0..279d479 100644 --- a/docs/PTHInternals.html +++ b/docs/PTHInternals.html @@ -23,38 +23,38 @@ implementation. If you are interested in the end-user view, please see the <a href="UsersManual.html#precompiledheaders">User's Manual</a>.</p> -<h2>Using Pretokenized Headers with <tt>clang-cc</tt> (Low-level Interface)</h2> +<h2>Using Pretokenized Headers with <tt>clang</tt> (Low-level Interface)</h2> -<p>The low-level Clang compiler tool, <tt>clang-cc</tt>, supports three command -line options for generating and using PTH files.<p> +<p>The Clang compiler frontend, <tt>clang -cc1</tt>, supports three command line +options for generating and using PTH files.<p> -<p>To generate PTH files using <tt>clang-cc</tt>, use the option +<p>To generate PTH files using <tt>clang -cc1</tt>, use the option <b><tt>-emit-pth</tt></b>: -<pre> $ clang-cc test.h -emit-pth -o test.h.pth </pre> +<pre> $ clang -cc1 test.h -emit-pth -o test.h.pth </pre> <p>This option is transparently used by <tt>clang</tt> when generating PTH files. Similarly, PTH files can be used as prefix headers using the <b><tt>-include-pth</tt></b> option:</p> <pre> - $ clang-cc -include-pth test.h.pth test.c -o test.s + $ clang -cc1 -include-pth test.h.pth test.c -o test.s </pre> <p>Alternatively, Clang's PTH files can be used as a raw "token-cache" (or "content" cache) of the source included by the original header file. This means that the contents of the PTH file are searched as substitutes -for <em>any</em> source files that are used by <tt>clang-cc</tt> to process a +for <em>any</em> source files that are used by <tt>clang -cc1</tt> to process a source file. This is done by specifying the <b><tt>-token-cache</tt></b> option:</p> <pre> $ cat test.h #include <stdio.h> - $ clang-cc -emit-pth test.h -o test.h.pth + $ clang -cc1 -emit-pth test.h -o test.h.pth $ cat test.c #include "test.h" - $ clang-cc test.c -o test -token-cache test.h.pth + $ clang -cc1 test.c -o test -token-cache test.h.pth </pre> <p>In this example the contents of <tt>stdio.h</tt> (and the files it includes) @@ -117,7 +117,7 @@ PTH file needs to be generated during a build instead of several.</p></li> <li><p><b>Reduced memory pressure</b>: Similar to GCC, Clang reads PTH files via the use of memory mapping (i.e., <tt>mmap</tt>). Clang, however, memory maps PTH files as read-only, meaning that multiple -invocations of <tt>clang-cc</tt> can share the same pages in memory from a +invocations of <tt>clang -cc1</tt> can share the same pages in memory from a memory-mapped PTH file. In comparison, GCC also memory maps its PCH files but also modifies those pages in memory, incurring the copy-on-write costs. The read-only nature of PTH can greatly reduce memory pressure for builds involving @@ -160,7 +160,7 @@ optimizations to speed up the processing of header files:</p> <ul> <li><p><em><tt>stat</tt> caching</em>: PTH files cache information obtained via -calls to <tt>stat</tt> that <tt>clang-cc</tt> uses to resolve which files are +calls to <tt>stat</tt> that <tt>clang -cc1</tt> uses to resolve which files are included by <tt>#include</tt> directives. This greatly reduces the overhead involved in context-switching to the kernel to resolve included files.</p></li> diff --git a/docs/UsersManual.html b/docs/UsersManual.html index cfaa071..b5aa6a8 100644 --- a/docs/UsersManual.html +++ b/docs/UsersManual.html @@ -40,6 +40,7 @@ td { <li><a href="#diagnostics_pragmas">Controlling Diagnostics via Pragmas</a></li> </ul> <li><a href="#precompiledheaders">Precompiled Headers</a></li> + <li><a href="#codegen">Controlling Code Generation</a></li> </ul> </li> <li><a href="#c">C Language Features</a> @@ -562,6 +563,29 @@ at the time of PCH use requires one of the PCH optimizations, <code>stat()</code> caching, to be disabled. However, this change is only likely to affect PCH files that reference a large number of headers.</p> +<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = --> +<h3 id="codegen">Controlling Code Generation</h3> +<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = --> + +<p>Clang provides a number of ways to control code generation. The options are listed below.</p> + +<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> +<dt id="opt_fcatch-undefined-behavior"><b>-fcatch-undefined-behavior</b>: Turn +on runtime code generation to check for undefined behavior.</dt> + +<dd>This option, which defaults to off, controls whether or not Clang +adds runtime checks for undefined runtime behavior. If the check fails, +<tt>__builtin_trap()</tt> is used to indicate failure. +The checks are: +<p> +<li>Subscripting where the static type of one operand is decayed from an + array type and the other operand is greater than the size of the array or + less than zero.</li> +<li>Shift operators where the amount shifted is greater or equal to the + promoted bit-width of the left-hand-side or less than zero.</li> +</p> +</dd> + <!-- ======================================================================= --> <h2 id="c">C Language Features</h2> <!-- ======================================================================= --> diff --git a/docs/libIndex.html b/docs/libIndex.html index 5693de8..e722ee1 100644 --- a/docs/libIndex.html +++ b/docs/libIndex.html @@ -211,8 +211,8 @@ void bar_func(void) { You first get AST files out of <code>t1.c</code> and <code>t2.c</code>: <pre class="code_example"> -$ clang-cc -emit-pch t1.c -o t1.ast -$ clang-cc -emit-pch t2.c -o t2.ast +$ clang -emit-ast t1.c -o t1.ast +$ clang -emit-ast t2.c -o t2.ast </pre> </p> |
