---
docs/UsersManual.html | 92 ++++++++++++++++++++++++++++---------------------
1 files changed, 53 insertions(+), 39 deletions(-)
diff --git a/docs/UsersManual.html b/docs/UsersManual.html
index 82c4fa2..8b74d3d 100644
--- a/docs/UsersManual.html
+++ b/docs/UsersManual.html
@@ -115,7 +115,7 @@ Microsoft, and other popular compilers as well as to improve functionality
through Clang-specific features. The Clang driver and language features are
intentionally designed to be as compatible with the GNU GCC compiler as
reasonably possible, easing migration from GCC to Clang. In most cases, code
-"just works".</p>
+"just works".</p>
<p>In addition to language specific features, Clang has a variety of features
that depend on what CPU architecture or operating system is being compiled for.
@@ -171,9 +171,9 @@ introduces the language selection and other high level options like -c, -g, etc.
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<p><b>-Werror</b>: Turn warnings into errors.</p>
-<p><b>-Werror=foo</b>: Turn warning "foo" into an error.</p>
-<p><b>-Wno-error=foo</b>: Turn warning "foo" into an warning even if -Werror is
- specified.</p>
+<p><b>-Werror=foo</b>: Turn warning "foo" into an error.</p>
+<p><b>-Wno-error=foo</b>: Turn warning "foo" into an warning even if
+ -Werror is specified.</p>
<p><b>-Wfoo</b>: Enable warning foo</p>
<p><b>-Wno-foo</b>: Disable warning foo</p>
<p><b>-w</b>: Disable all warnings.</p>
@@ -214,8 +214,8 @@ print something like:</p>
//
</pre>
-<p>When this is disabled, Clang will print "test.c:28: warning..." with no
-column number.</p>
+<p>When this is disabled, Clang will print "test.c:28: warning..."
+with no column number.</p>
</dd>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
@@ -232,7 +232,8 @@ when this is enabled, Clang will print something like:</p>
//
</pre>
-<p>When this is disabled, Clang will not print the "test.c:28:8: " part.</p>
+<p>When this is disabled, Clang will not print the "test.c:28:8: "
+part.</p>
</dd>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
@@ -295,7 +296,7 @@ href="#pragma_GCC_diagnostic">#pragma GCC diagnostic</a>.</dd>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<dt id="opt_fdiagnostics-show-category"><b>-fdiagnostics-show-category=none/id/name</b>:
Enable printing category information in diagnostic line.</dt>
-<dd>This option, which defaults to "none",
+<dd>This option, which defaults to "none",
controls whether or not Clang prints the category associated with a diagnostic
when emitting it. Each diagnostic may or many not have an associated category,
if it has one, it is listed in the diagnostic categorization field of the
@@ -319,7 +320,7 @@ hundreds or thousands of them.</p>
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<dt id="opt_fdiagnostics-fixit-info"><b>-f[no-]diagnostics-fixit-info</b>:
-Enable "FixIt" information in the diagnostics output.</dt>
+Enable "FixIt" information in the diagnostics output.</dt>
<dd>This option, which defaults to on, controls whether or not Clang prints the
information on how to fix a specific diagnostic underneath it when it knows.
For example, in this output:</p>
@@ -332,7 +333,8 @@ For example, in this output:</p>
</pre>
<p>Passing <b>-fno-diagnostics-fixit-info</b> will prevent Clang from printing
-the "//" line at the end of the message. This information is useful for users
+the "//" line at the end of the message.
+This information is useful for users
who may not understand what is wrong, but can be confusing for machine
parsing.</p>
</dd>
@@ -363,10 +365,17 @@ Print Fix-Its in a machine parseable form.</dt>
<dd><p>This option makes Clang print available Fix-Its in a machine parseable format at the end of diagnostics. The following example illustrates the format:</p>
<pre>
- fix-it:"t.cpp":{7:25-7:29}:"Gamma"
+ fix-it:"t.cpp":{7:25-7:29}:"Gamma"
</pre>
-<p>The range printed is a half-open range, so in this example the characters at column 25 up to but not including column 29 on line 7 in t.cpp should be replaced with the string "Gamma". Either the range or the replacement string may be empty (representing strict insertions and strict erasures, respectively). Both the file name and the insertion string escape backslash (as "\\"), tabs (as "\t"), newlines (as "\n"), double quotes(as "\"") and non-printable characters (as octal "\xxx").</p>
+<p>The range printed is a half-open range, so in this example the characters at
+column 25 up to but not including column 29 on line 7 in t.cpp should be
+replaced with the string "Gamma". Either the range or the replacement
+string may be empty (representing strict insertions and strict erasures,
+respectively). Both the file name and the insertion string escape backslash
+(as "\\"), tabs (as "\t"), newlines (as "\n"),
+double quotes(as "\"") and non-printable characters
+(as octal "\xxx").</p>
</dd>
</dl>
@@ -502,8 +511,8 @@ it:</p>
<li>The line of source code that the issue occurs on, along with a caret and
ranges that indicate the important locations [<a
href="opt_fcaret-diagnostics">-fcaret-diagnostics</a>].</li>
-<li>"FixIt" information, which is a concise explanation of how to fix the
- problem (when Clang is certain it knows) [<a
+<li>"FixIt" information, which is a concise explanation of how to fix
+ the problem (when Clang is certain it knows) [<a
href="opt_fdiagnostics-fixit-info">-fdiagnostics-fixit-info</a>].</li>
<li>A machine-parsable representation of the ranges involved (off by
default) [<a
@@ -536,8 +545,9 @@ Diagnostics</a>.</p>
<p>Categories are not shown by default, but they can be turned on with the
<a href="#opt_fdiagnostics-show-category">-fdiagnostics-show-category</a> option.
-When set to "<tt>name</tt>", the category is printed textually in the diagnostic
-output. When it is set to "<tt>id</tt>", a category number is printed. The
+When set to "<tt>name</tt>", the category is printed textually in the
+diagnostic output.
+When it is set to "<tt>id</tt>", a category number is printed. The
mapping of category names to category id's can be obtained by running '<tt>clang
--print-diagnostic-categories</tt>'.
</p>
@@ -559,7 +569,7 @@ Warnings may be set to ignored, warning, error, or fatal. The following
example code will tell Clang or GCC to ignore the -Wall warnings:</p>
<pre>
-#pragma GCC diagnostic ignored "-Wall"
+#pragma GCC diagnostic ignored "-Wall"
</pre>
<p>In addition to all of the functionality provided by GCC's pragma, Clang
@@ -573,7 +583,7 @@ diagnostics return to whatever state had previously existed.</p>
<pre>
#pragma clang diagnostic push
-#pragma clang diagnostic ignored "-Wmultichar"
+#pragma clang diagnostic ignored "-Wmultichar"
char b = 'df'; // no warning.
@@ -675,7 +685,7 @@ for headers that are directly included within a source file. For example:</p>
<pre>
$ clang -x c-header test.h -o test.h.pch
$ cat test.c
- #include "test.h"
+ #include "test.h"
$ clang test.c -o test
</pre>
@@ -687,8 +697,9 @@ and not specified on the command line using <tt>-include</tt>.</p>
<p>It is sometimes necessary to build a precompiled header from headers that
are not yet in their final, installed locations. For example, one might build a
precompiled header within the build tree that is then meant to be installed
-alongside the headers. Clang permits the creation of "relocatable" precompiled
-headers, which are built with a given path (into the build directory) and can
+alongside the headers. Clang permits the creation of "relocatable"
+precompiled headers,
+which are built with a given path (into the build directory) and can
later be used from an installed location.</p>
<p>To build a relocatable precompiled header, place your headers into a
@@ -785,29 +796,32 @@ for those modes. If no -std option is specified, clang defaults to gnu99 mode.
<p>Differences between all c* and gnu* modes:</p>
<ul>
-<li>c* modes define "__STRICT_ANSI__".</li>
-<li>Target-specific defines not prefixed by underscores, like "linux", are
-defined in gnu* modes.</li>
+<li>c* modes define "__STRICT_ANSI__".</li>
+<li>Target-specific defines not prefixed by underscores, like "linux",
+are defined in gnu* modes.</li>
<li>Trigraphs default to being off in gnu* modes; they can be enabled by the
-trigraphs option.</li>
-<li>The parser recognizes "asm" and "typeof" as keywords in gnu* modes; the
-variants "__asm__" and "__typeof__" are recognized in all modes.</li>
-<li>The Apple "blocks" extension is recognized by default in gnu* modes
-on some platforms; it can be enabled in any mode with the "-fblocks"
+<li>The parser recognizes "asm" and "typeof" as keywords in
+gnu* modes; the variants "__asm__" and "__typeof__" are
+recognized in all modes.</li>
+<li>The Apple "blocks" extension is recognized by default in gnu*
+modes
+on some platforms; it can be enabled in any mode with the "-fblocks"
option.</li>
</ul>
<p>Differences between *89 and *99 modes:</p>
<ul>
-<li>The *99 modes default to implementing "inline" as specified in C99, while
-the *89 modes implement the GNU version. This can be overridden for individual
-functions with the __gnu_inline__ attribute.</li>
+<li>The *99 modes default to implementing "inline" as specified in
+C99, while the *89 modes implement the GNU version. This can be overridden for
+individual functions with the __gnu_inline__ attribute.</li>
<li>Digraphs are not recognized in c89 mode.</li>
-<li>The scope of names defined inside a "for", "if", "switch", "while", or "do"
-statement is different. (example: "if ((struct x {int x;}*)0) {}".)</li>
+<li>The scope of names defined inside a "for", "if",
+"switch", "while", or "do" statement is different.
+(example: "if ((struct x {int x;}*)0) {}".)</li>
<li>__STDC_VERSION__ is not defined in *89 modes.</li>
-<li>"inline" is not recognized as a keyword in c89 mode.</li>
-<li>"restrict" is not recognized as a keyword in *89 modes.</li>
+<li>"inline" is not recognized as a keyword in c89 mode.</li>
+<li>"restrict" is not recognized as a keyword in *89 modes.</li>
<li>Commas are allowed in integer constant expressions in *99 modes.</li>
<li>Arrays which are not lvalues are not implicitly promoted to pointers in
*89 modes.</li>
@@ -892,10 +906,10 @@ at most one definition for each function. Source code using this feature should
be changed to define the inline and out-of-line definitions in separate
translation units.</li>
-<li>clang does not have an equivalent to gcc's "fold"; this means that
+<li>clang does not have an equivalent to gcc's "fold"; this means that
clang doesn't accept some constructs gcc might accept in contexts where a
-constant expression is required, like "x-x" where x is a variable, or calls
-to C library functions like strlen.</li>
+constant expression is required, like "x-x" where x is a variable,
+or calls to C library functions like strlen.</li>
<li>clang does not support multiple alternative constraints in inline asm; this
is an extremely obscure feature which would be complicated to implement
@@ -926,7 +940,7 @@ headers.</li>
<li>clang does not support the Microsoft extension where anonymous
record members can be declared using user defined typedefs.</li>
-<li>clang supports the Microsoft "#pragma pack" feature for
+<li>clang supports the Microsoft "#pragma pack" feature for
controlling record layout. GCC also contains support for this feature,
however where MSVC and GCC are incompatible clang follows the MSVC
definition.</li>
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
