Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / clang / 1bf908df57cc43f3bc7296f4e51f5708bd323c6b / . / docs / UsersManual.html
blob: a0e5ed8e8c60259ef754e17da4f2ae1cb8d8a22e [file] [log] [blame]
Benjamin Kramer665a8dc2012-01-15 15:26:07 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]3<html>
4<head>
5<title>Clang Compiler User's Manual</title>
Benjamin Kramer665a8dc2012-01-15 15:26:07 +0000[diff] [blame]6<link type="text/css" rel="stylesheet" href="../menu.css">
7<link type="text/css" rel="stylesheet" href="../content.css">
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]8<style type="text/css">
9td {
10 vertical-align: top;
11}
12</style>
13</head>
14<body>
15
16<!--#include virtual="../menu.html.incl"-->
17
18<div id="content">
19
20<h1>Clang Compiler User's Manual</h1>
21
22<ul>
23<li><a href="#intro">Introduction</a>
24 <ul>
25 <li><a href="#terminology">Terminology</a></li>
26 <li><a href="#basicusage">Basic Usage</a></li>
27 </ul>
28</li>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]29<li><a href="#commandline">Command Line Options</a>
30 <ul>
31 <li><a href="#cl_diagnostics">Options to Control Error and Warning
32 Messages</a></li>
Chad Rosierb211a4b2012-02-22 19:14:46 +0000[diff] [blame]33 <li><a href="#cl_crash_diagnostics">Options to Control Clang Crash
34 Diagnostics</a></li>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]35 </ul>
36</li>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]37<li><a href="#general_features">Language and Target-Independent Features</a>
38 <ul>
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]39 <li><a href="#diagnostics">Controlling Errors and Warnings</a>
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]40 <ul>
41 <li><a href="#diagnostics_display">Controlling How Clang Displays Diagnostics</a></li>
42 <li><a href="#diagnostics_mappings">Diagnostic Mappings</a></li>
Chris Lattner67db8cd2010-05-30 23:42:51 +0000[diff] [blame]43 <li><a href="#diagnostics_categories">Diagnostic Categories</a></li>
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]44 <li><a href="#diagnostics_commandline">Controlling Diagnostics via Command Line Flags</a></li>
45 <li><a href="#diagnostics_pragmas">Controlling Diagnostics via Pragmas</a></li>
Richard Smithf122a132012-06-13 20:27:03 +0000[diff] [blame]46 <li><a href="#diagnostics_systemheader">Controlling Diagnostics in System Headers</a></li>
Ted Kremenekf391fa72011-08-18 01:17:05 +0000[diff] [blame]47 <li><a href="#diagnostics_enable_everything">Enabling All Warnings</a></li>
Ted Kremenek2fb11eb2010-08-24 18:12:35 +0000[diff] [blame]48 <li><a href="#analyzer_diagnositics">Controlling Static Analyzer Diagnostics</a></li>
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]49 </ul>
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]50 </li>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]51 <li><a href="#precompiledheaders">Precompiled Headers</a></li>
Mike Stump53664ca2009-12-14 23:53:10 +0000[diff] [blame]52 <li><a href="#codegen">Controlling Code Generation</a></li>
Alexey Samsonov5ab52492012-05-30 06:55:10 +0000[diff] [blame]53 <li><a href="#debuginfosize">Controlling Size of Debug Information</a></li>
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]54 </ul>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]55</li>
56<li><a href="#c">C Language Features</a>
57 <ul>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]58 <li><a href="#c_ext">Extensions supported by clang</a></li>
59 <li><a href="#c_modes">Differences between various standard modes</a></li>
60 <li><a href="#c_unimpl_gcc">GCC extensions not implemented yet</a></li>
61 <li><a href="#c_unsupp_gcc">Intentionally unsupported GCC extensions</a></li>
62 <li><a href="#c_ms">Microsoft extensions</a></li>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]63 </ul>
64</li>
Richard Smithbdb10182011-11-21 20:54:59 +0000[diff] [blame]65<li><a href="#cxx">C++ Language Features</a>
66 <ul>
67 <li><a href="#cxx_implimits">Controlling implementation limits</a></li>
68 </ul>
69</li>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]70<li><a href="#target_features">Target-Specific Features and Limitations</a>
71 <ul>
72 <li><a href="#target_arch">CPU Architectures Features and Limitations</a>
73 <ul>
74 <li><a href="#target_arch_x86">X86</a></li>
Eli Friedman3b658d32009-06-08 05:12:39 +0000[diff] [blame]75 <li><a href="#target_arch_arm">ARM</a></li>
76 <li><a href="#target_arch_other">Other platforms</a></li>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]77 </ul>
78 </li>
79 <li><a href="#target_os">Operating System Features and Limitations</a>
80 <ul>
81 <li><a href="#target_os_darwin">Darwin (Mac OS/X)</a></li>
82 <li>Linux, etc.</li>
NAKAMURA Takumia75fdb22011-04-04 15:02:41 +0000[diff] [blame]83 <li><a href="#target_os_win32">Windows</a></li>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]84 </ul>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]85 </li>
86 </ul>
87</li>
88</ul>
89
90
91<!-- ======================================================================= -->
92<h2 id="intro">Introduction</h2>
93<!-- ======================================================================= -->
94
95<p>The Clang Compiler is an open-source compiler for the C family of programming
96languages, aiming to be the best in class implementation of these languages.
97Clang builds on the LLVM optimizer and code generator, allowing it to provide
98high-quality optimization and code generation support for many targets. For
99more general information, please see the <a href="http://clang.llvm.org">Clang
100Web Site</a> or the <a href="http://llvm.org">LLVM Web Site</a>.</p>
101
102<p>This document describes important notes about using Clang as a compiler for
103an end-user, documenting the supported features, command line options, etc. If
104you are interested in using Clang to build a tool that processes code, please
105see <a href="InternalsManual.html">the Clang Internals Manual</a>. If you are
Michael J. Spencer8275fc02012-02-12 09:11:39 +0000[diff] [blame]106interested in the <a href="http://clang-analyzer.llvm.org">Clang
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]107Static Analyzer</a>, please see its web page.</p>
108
109<p>Clang is designed to support the C family of programming languages, which
110includes <a href="#c">C</a>, <a href="#objc">Objective-C</a>, <a
111href="#cxx">C++</a>, and <a href="#objcxx">Objective-C++</a> as well as many
112dialects of those. For language-specific information, please see the
113corresponding language specific section:</p>
114
115<ul>
116<li><a href="#c">C Language</a>: K&amp;R C, ANSI C89, ISO C90, ISO C94
117 (C89+AMD1), ISO C99 (+TC1, TC2, TC3). </li>
118<li><a href="#objc">Objective-C Language</a>: ObjC 1, ObjC 2, ObjC 2.1, plus
119 variants depending on base language.</li>
Richard Smithbdb10182011-11-21 20:54:59 +0000[diff] [blame]120<li><a href="#cxx">C++ Language</a></li>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]121<li><a href="#objcxx">Objective C++ Language</a></li>
122</ul>
123
124<p>In addition to these base languages and their dialects, Clang supports a
125broad variety of language extensions, which are documented in the corresponding
126language section. These extensions are provided to be compatible with the GCC,
127Microsoft, and other popular compilers as well as to improve functionality
128through Clang-specific features. The Clang driver and language features are
129intentionally designed to be as compatible with the GNU GCC compiler as
130reasonably possible, easing migration from GCC to Clang. In most cases, code
131"just works".</p>
132
133<p>In addition to language specific features, Clang has a variety of features
134that depend on what CPU architecture or operating system is being compiled for.
Douglas Gregorcd5a5052009-11-09 15:15:41 +0000[diff] [blame]135Please see the <a href="#target_features">Target-Specific Features and
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]136Limitations</a> section for more details.</p>
137
138<p>The rest of the introduction introduces some basic <a
139href="#terminology">compiler terminology</a> that is used throughout this manual
140and contains a basic <a href="#basicusage">introduction to using Clang</a>
141as a command line compiler.</p>
142
143<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
144<h3 id="terminology">Terminology</h3>
145<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
146
147<p>Front end, parser, backend, preprocessor, undefined behavior, diagnostic,
148 optimizer</p>
149
150<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
151<h3 id="basicusage">Basic Usage</h3>
152<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
153
154<p>Intro to how to use a C compiler for newbies.</p>
155<p>
156compile + link
157
158compile then link
159
160debug info
161
162enabling optimizations
163
164picking a language to use, defaults to C99 by default. Autosenses based on
165extension.
166
167using a makefile
168</p>
169
170
171<!-- ======================================================================= -->
172<h2 id="commandline">Command Line Options</h2>
173<!-- ======================================================================= -->
174
175<p>
176This section is generally an index into other sections. It does not go into
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]177depth on the ones that are covered by other sections. However, the first part
178introduces the language selection and other high level options like -c, -g, etc.
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]179</p>
180
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]181
182<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
183<h3 id="cl_diagnostics">Options to Control Error and Warning Messages</h3>
184<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
185
186<p><b>-Werror</b>: Turn warnings into errors.</p>
187<p><b>-Werror=foo</b>: Turn warning "foo" into an error.</p>
188<p><b>-Wno-error=foo</b>: Turn warning "foo" into an warning even if -Werror is
189 specified.</p>
190<p><b>-Wfoo</b>: Enable warning foo</p>
191<p><b>-Wno-foo</b>: Disable warning foo</p>
192<p><b>-w</b>: Disable all warnings.</p>
193<p><b>-pedantic</b>: Warn on language extensions.</p>
194<p><b>-pedantic-errors</b>: Error on language extensions.</p>
195<p><b>-Wsystem-headers</b>: Enable warnings from system headers.</p>
196
Chris Lattner0f0c9632010-04-07 20:49:23 +0000[diff] [blame]197<p><b>-ferror-limit=123</b>: Stop emitting diagnostics after 123 errors have
198 been produced. The default is 20, and the error limit can be disabled with
199 -ferror-limit=0.</p>
200
Douglas Gregor575cf372010-04-20 07:18:24 +0000[diff] [blame]201<p><b>-ftemplate-backtrace-limit=123</b>: Only emit up to 123 template instantiation notes within the template instantiation backtrace for a single warning or error. The default is 10, and the limit can be disabled with -ftemplate-backtrace-limit=0.</p>
202
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]203<!-- ================================================= -->
204<h4 id="cl_diag_formatting">Formatting of Diagnostics</h4>
205<!-- ================================================= -->
206
207<p>Clang aims to produce beautiful diagnostics by default, particularly for new
208users that first come to Clang. However, different people have different
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]209preferences, and sometimes Clang is driven by another program that wants to
210parse simple and consistent output, not a person. For these cases, Clang
211provides a wide range of options to control the exact output format of the
212diagnostics that it generates.</p>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]213
214<dl>
215
216<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
217<dt id="opt_fshow-column"><b>-f[no-]show-column</b>: Print column number in
218diagnostic.</dt>
219<dd>This option, which defaults to on, controls whether or not Clang prints the
220column number of a diagnostic. For example, when this is enabled, Clang will
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]221print something like:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]222
223<pre>
224 test.c:28:8: warning: extra tokens at end of #endif directive [-Wextra-tokens]
225 #endif bad
226 ^
227 //
228</pre>
229
230<p>When this is disabled, Clang will print "test.c:28: warning..." with no
231column number.</p>
232</dd>
233
234<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
235<dt id="opt_fshow-source-location"><b>-f[no-]show-source-location</b>: Print
236source file/line/column information in diagnostic.</dt>
237<dd>This option, which defaults to on, controls whether or not Clang prints the
238filename, line number and column number of a diagnostic. For example,
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]239when this is enabled, Clang will print something like:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]240
241<pre>
242 test.c:28:8: warning: extra tokens at end of #endif directive [-Wextra-tokens]
243 #endif bad
244 ^
245 //
246</pre>
247
248<p>When this is disabled, Clang will not print the "test.c:28:8: " part.</p>
249</dd>
250
251<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
252<dt id="opt_fcaret-diagnostics"><b>-f[no-]caret-diagnostics</b>: Print source
253line and ranges from source code in diagnostic.</dt>
254<dd>This option, which defaults to on, controls whether or not Clang prints the
255source line, source ranges, and caret when emitting a diagnostic. For example,
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]256when this is enabled, Clang will print something like:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]257
258<pre>
259 test.c:28:8: warning: extra tokens at end of #endif directive [-Wextra-tokens]
260 #endif bad
261 ^
262 //
263</pre>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]264</dd>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]265<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
Douglas Gregore8d44dd2010-07-09 16:31:58 +0000[diff] [blame]266<dt id="opt_fcolor_diagnostics"><b>-f[no-]color-diagnostics</b>: </dt>
267<dd>This option, which defaults to on when a color-capable terminal is
268 detected, controls whether or not Clang prints diagnostics in color.
269 When this option is enabled, Clang will use colors to highlight
270 specific parts of the diagnostic, e.g.,
Chris Lattner4e1c53d2011-01-24 03:47:34 +0000[diff] [blame]271 <pre>
Benjamin Kramer665a8dc2012-01-15 15:26:07 +0000[diff] [blame]272 <b><span style="color:black">test.c:28:8: <span style="color:magenta">warning</span>: extra tokens at end of #endif directive [-Wextra-tokens]</span></b>
Chris Lattner4e1c53d2011-01-24 03:47:34 +0000[diff] [blame]273 #endif bad
Benjamin Kramer665a8dc2012-01-15 15:26:07 +0000[diff] [blame]274 <span style="color:green">^</span>
275 <span style="color:green">//</span>
Douglas Gregore8d44dd2010-07-09 16:31:58 +0000[diff] [blame]276</pre>
Chris Lattner4e1c53d2011-01-24 03:47:34 +0000[diff] [blame]277
278<p>When this is disabled, Clang will just print:</p>
279
280<pre>
281 test.c:2:8: warning: extra tokens at end of #endif directive [-Wextra-tokens]
282 #endif bad
283 ^
284 //
285</pre>
286</dd>
Douglas Gregore8d44dd2010-07-09 16:31:58 +0000[diff] [blame]287<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
Douglas Gregorc9471b02011-05-21 17:07:29 +0000[diff] [blame]288<dt id="opt_fdiagnostics-format"><b>-fdiagnostics-format=clang/msvc/vi</b>:
289Changes diagnostic output format to better match IDEs and command line tools.</dt>
290<dd>This option controls the output format of the filename, line number, and column printed in diagnostic messages. The options, and their affect on formatting a simple conversion diagnostic, follow:
291
292 <dl>
293 <dt><b>clang</b> (default)</dt>
294 <dd>
295 <pre>t.c:3:11: warning: conversion specifies type 'char *' but the argument has type 'int'</pre>
296 </dd>
297
298 <dt><b>msvc</b></dt>
299 <dd>
300 <pre>t.c(3,11) : warning: conversion specifies type 'char *' but the argument has type 'int'</pre>
301 </dd>
302
303 <dt><b>vi</b></dt>
304 <dd>
305 <pre>t.c +3:11: warning: conversion specifies type 'char *' but the argument has type 'int'</pre>
306 </dd>
307 </dl>
308</dd>
309
310<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
Argyrios Kyrtzidis477aab62011-05-25 05:05:01 +0000[diff] [blame]311<dt id="opt_fdiagnostics-show-name"><b>-f[no-]diagnostics-show-name</b>:
312Enable the display of the diagnostic name.</dt>
313<dd>This option, which defaults to off, controls whether or not
Benjamin Kramer665a8dc2012-01-15 15:26:07 +0000[diff] [blame]314Clang prints the associated name.<p></p></dd>
Argyrios Kyrtzidis477aab62011-05-25 05:05:01 +0000[diff] [blame]315<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]316<dt id="opt_fdiagnostics-show-option"><b>-f[no-]diagnostics-show-option</b>:
317Enable <tt>[-Woption]</tt> information in diagnostic line.</dt>
318<dd>This option, which defaults to on,
319controls whether or not Clang prints the associated <A
320href="#cl_diag_warning_groups">warning group</a> option name when outputting
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]321a warning diagnostic. For example, in this output:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]322
323<pre>
324 test.c:28:8: warning: extra tokens at end of #endif directive [-Wextra-tokens]
325 #endif bad
326 ^
327 //
328</pre>
329
330<p>Passing <b>-fno-diagnostics-show-option</b> will prevent Clang from printing
331the [<a href="#opt_Wextra-tokens">-Wextra-tokens</a>] information in the
332diagnostic. This information tells you the flag needed to enable or disable the
333diagnostic, either from the command line or through <a
334href="#pragma_GCC_diagnostic">#pragma GCC diagnostic</a>.</dd>
335
Chris Lattner28a43a42010-05-05 01:35:28 +0000[diff] [blame]336<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
337<dt id="opt_fdiagnostics-show-category"><b>-fdiagnostics-show-category=none/id/name</b>:
338Enable printing category information in diagnostic line.</dt>
339<dd>This option, which defaults to "none",
340controls whether or not Clang prints the category associated with a diagnostic
341when emitting it. Each diagnostic may or many not have an associated category,
342if it has one, it is listed in the diagnostic categorization field of the
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]343diagnostic line (in the []'s).
Chris Lattner28a43a42010-05-05 01:35:28 +0000[diff] [blame]344
345<p>For example, a format string warning will produce these three renditions
346based on the setting of this option:</p>
347
348<pre>
349 t.c:3:11: warning: conversion specifies type 'char *' but the argument has type 'int' [-Wformat]
350 t.c:3:11: warning: conversion specifies type 'char *' but the argument has type 'int' [-Wformat<b>,1</b>]
351 t.c:3:11: warning: conversion specifies type 'char *' but the argument has type 'int' [-Wformat<b>,Format String</b>]
352</pre>
353
354<p>This category can be used by clients that want to group diagnostics by
355category, so it should be a high level category. We want dozens of these, not
356hundreds or thousands of them.</p>
357</dd>
358
359
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]360
361<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
362<dt id="opt_fdiagnostics-fixit-info"><b>-f[no-]diagnostics-fixit-info</b>:
363Enable "FixIt" information in the diagnostics output.</dt>
364<dd>This option, which defaults to on, controls whether or not Clang prints the
365information on how to fix a specific diagnostic underneath it when it knows.
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]366For example, in this output:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]367
368<pre>
369 test.c:28:8: warning: extra tokens at end of #endif directive [-Wextra-tokens]
370 #endif bad
371 ^
372 //
373</pre>
374
375<p>Passing <b>-fno-diagnostics-fixit-info</b> will prevent Clang from printing
376the "//" line at the end of the message. This information is useful for users
377who may not understand what is wrong, but can be confusing for machine
378parsing.</p>
379</dd>
380
381<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
Chris Lattner2a9cc232009-04-21 05:35:32 +0000[diff] [blame]382<dt id="opt_fdiagnostics-print-source-range-info">
383<b>-f[no-]diagnostics-print-source-range-info</b>:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]384Print machine parsable information about source ranges.</dt>
385<dd>This option, which defaults to off, controls whether or not Clang prints
386information about source ranges in a machine parsable format after the
387file/line/column number information. The information is a simple sequence of
388brace enclosed ranges, where each range lists the start and end line/column
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]389locations. For example, in this output:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]390
391<pre>
392exprs.c:47:15:{47:8-47:14}{47:17-47:24}: error: invalid operands to binary expression ('int *' and '_Complex float')
393 P = (P-42) + Gamma*4;
394 ~~~~~~ ^ ~~~~~~~
395</pre>
396
Chris Lattner2a9cc232009-04-21 05:35:32 +0000[diff] [blame]397<p>The {}'s are generated by -fdiagnostics-print-source-range-info.</p>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]398</dd>
399
Douglas Gregor4786c152010-08-19 20:24:43 +0000[diff] [blame]400<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
401<dt id="opt_fdiagnostics-parseable-fixits">
402<b>-fdiagnostics-parseable-fixits</b>:
403Print Fix-Its in a machine parseable form.</dt>
404<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>
405
406<pre>
Douglas Gregorbf5e09d2010-08-20 03:17:33 +0000[diff] [blame]407 fix-it:"t.cpp":{7:25-7:29}:"Gamma"
Douglas Gregor4786c152010-08-19 20:24:43 +0000[diff] [blame]408</pre>
409
NAKAMURA Takumi44626362011-04-05 00:57:02 +0000[diff] [blame]410<p>The range printed is a half-open range, so in this example the characters at
411column 25 up to but not including column 29 on line 7 in t.cpp should be
412replaced with the string &quot;Gamma&quot;. Either the range or the replacement
413string may be empty (representing strict insertions and strict erasures,
414respectively). Both the file name and the insertion string escape backslash (as
415&quot;\\&quot;), tabs (as &quot;\t&quot;), newlines (as &quot;\n&quot;), double
416quotes(as &quot;\&quot;&quot;) and non-printable characters (as octal
417&quot;\xxx&quot;).</p>
Douglas Gregor4786c152010-08-19 20:24:43 +0000[diff] [blame]418</dd>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]419
420</dl>
421
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]422
423
424<!-- ===================================================== -->
425<h4 id="cl_diag_warning_groups">Individual Warning Groups</h4>
426<!-- ===================================================== -->
427
428<p>TODO: Generate this from tblgen. Define one anchor per warning group.</p>
429
430
431<dl>
432
433
434<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
435<dt id="opt_Wextra-tokens"><b>-Wextra-tokens</b>: Warn about excess tokens at
436 the end of a preprocessor directive.</dt>
437<dd>This option, which defaults to on, enables warnings about extra tokens at
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]438the end of preprocessor directives. For example:
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]439
440<pre>
441 test.c:28:8: warning: extra tokens at end of #endif directive [-Wextra-tokens]
442 #endif bad
443 ^
444</pre>
445
446<p>These extra tokens are not strictly conforming, and are usually best handled
447by commenting them out.</p>
448
449<p>This option is also enabled by <a href="">-Wfoo</a>, <a href="">-Wbar</a>,
450 and <a href="">-Wbaz</a>.</p>
451</dd>
452
Jeffrey Yasskin21d07e42010-06-05 01:39:57 +0000[diff] [blame]453<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
454<dt id="opt_Wambiguous-member-template"><b>-Wambiguous-member-template</b>:
455Warn about unqualified uses of a member template whose name resolves
456to another template at the location of the use.</dt>
457<dd>This option, which defaults to on, enables a warning in the
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]458following code:
Jeffrey Yasskin21d07e42010-06-05 01:39:57 +0000[diff] [blame]459
460<pre>
461template&lt;typename T> struct set{};
462template&lt;typename T> struct trait { typedef const T& type; };
463struct Value {
464 template&lt;typename T> void set(typename trait&lt;T>::type value) {}
465};
466void foo() {
467 Value v;
468 v.set&lt;double>(3.2);
469}
470</pre>
471
472<p>C++ [basic.lookup.classref] requires this to be an error, but,
473because it's hard to work around, Clang downgrades it to a warning as
474an extension.</p>
475</dd>
476
Jeffrey Yasskin57d12fd2010-06-07 15:58:05 +0000[diff] [blame]477<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
478<dt id="opt_Wbind-to-temporary-copy"><b>-Wbind-to-temporary-copy</b>: Warn about
479an unusable copy constructor when binding a reference to a temporary.</dt>
480<dd>This option, which defaults to on, enables warnings about binding a
481reference to a temporary when the temporary doesn't have a usable copy
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]482constructor. For example:
Jeffrey Yasskin57d12fd2010-06-07 15:58:05 +0000[diff] [blame]483
484<pre>
485 struct NonCopyable {
486 NonCopyable();
487 private:
488 NonCopyable(const NonCopyable&);
489 };
490 void foo(const NonCopyable&);
491 void bar() {
David Blaikie5090e9f2011-10-18 05:49:30 +0000[diff] [blame]492 foo(NonCopyable()); // Disallowed in C++98; allowed in C++11.
Jeffrey Yasskin57d12fd2010-06-07 15:58:05 +0000[diff] [blame]493 }
494</pre>
495<pre>
496 struct NonCopyable2 {
497 NonCopyable2();
498 NonCopyable2(NonCopyable2&);
499 };
500 void foo(const NonCopyable2&);
501 void bar() {
David Blaikie5090e9f2011-10-18 05:49:30 +0000[diff] [blame]502 foo(NonCopyable2()); // Disallowed in C++98; allowed in C++11.
Jeffrey Yasskin57d12fd2010-06-07 15:58:05 +0000[diff] [blame]503 }
504</pre>
505
506<p>Note that if <tt>NonCopyable2::NonCopyable2()</tt> has a default
507argument whose instantiation produces a compile error, that error will
508still be a hard error in C++98 mode even if this warning is turned
509off.</p>
510
511</dd>
512
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]513</dl>
514
Chad Rosiercd376a12012-02-22 20:26:10 +0000[diff] [blame]515<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
516<h3 id="cl_crash_diagnostics">Options to Control Clang Crash Diagnostics</h3>
517<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
518
519<p>As unbelievable as it may sound, Clang does crash from time to time.
520Generally, this only occurs to those living on the
521<a href="http://llvm.org/releases/download.html#svn">bleeding edge</a>. Clang
522goes to great lengths to assist you in filing a bug report. Specifically, Clang
523generates preprocessed source file(s) and associated run script(s) upon a
524crash. These files should be attached to a bug report to ease reproducibility
525of the failure. Below are the command line options to control the crash
526diagnostics.
527</p>
528
529<p><b>-fno-crash-diagnostics</b>: Disable auto-generation of preprocessed
530source files during a clang crash.</p>
531
532<p>The -fno-crash-diagnostics flag can be helpful for speeding the process of
533generating a delta reduced test case.</p>
534
535
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]536<!-- ======================================================================= -->
537<h2 id="general_features">Language and Target-Independent Features</h2>
538<!-- ======================================================================= -->
539
540
541<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
542<h3 id="diagnostics">Controlling Errors and Warnings</h3>
543<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
544
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]545<p>Clang provides a number of ways to control which code constructs cause it to
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]546emit errors and warning messages, and how they are displayed to the console.</p>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]547
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]548<h4 id="diagnostics_display">Controlling How Clang Displays Diagnostics</h4>
Chris Lattner65a795b2009-04-20 06:00:23 +0000[diff] [blame]549
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]550<p>When Clang emits a diagnostic, it includes rich information in the output,
551and gives you fine-grain control over which information is printed. Clang has
552the ability to print this information, and these are the options that control
553it:</p>
554
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]555<ol>
556<li>A file/line/column indicator that shows exactly where the diagnostic occurs
557 in your code [<a href="#opt_fshow-column">-fshow-column</a>, <a
558 href="#opt_fshow-source-location">-fshow-source-location</a>].</li>
559<li>A categorization of the diagnostic as a note, warning, error, or fatal
560 error.</li>
561<li>A text string that describes what the problem is.</li>
562<li>An option that indicates how to control the diagnostic (for diagnostics that
563 support it) [<a
564 href="#opt_fdiagnostics-show-option">-fdiagnostics-show-option</a>].</li>
Chris Lattner3f145382010-05-24 21:35:18 +0000[diff] [blame]565<li>A <a href="#diagnostics_categories">high-level category</a> for the
566 diagnostic for clients that want to group diagnostics by class (for
567 diagnostics that support it) [<a
Chris Lattner28a43a42010-05-05 01:35:28 +0000[diff] [blame]568 href="#opt_fdiagnostics-show-category">-fdiagnostics-show-category</a>].</li>
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]569<li>The line of source code that the issue occurs on, along with a caret and
570 ranges that indicate the important locations [<a
571 href="opt_fcaret-diagnostics">-fcaret-diagnostics</a>].</li>
572<li>"FixIt" information, which is a concise explanation of how to fix the
573 problem (when Clang is certain it knows) [<a
574 href="opt_fdiagnostics-fixit-info">-fdiagnostics-fixit-info</a>].</li>
575<li>A machine-parsable representation of the ranges involved (off by
576 default) [<a
Chris Lattner2a9cc232009-04-21 05:35:32 +0000[diff] [blame]577 href="opt_fdiagnostics-print-source-range-info">-fdiagnostics-print-source-range-info</a>].</li>
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]578</ol>
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]579
580<p>For more information please see <a href="#cl_diag_formatting">Formatting of
581Diagnostics</a>.</p>
582
Chris Lattner3f145382010-05-24 21:35:18 +0000[diff] [blame]583
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]584<h4 id="diagnostics_mappings">Diagnostic Mappings</h4>
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]585
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]586<p>All diagnostics are mapped into one of these 5 classes:</p>
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]587
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]588<ul>
589<li>Ignored</li>
590<li>Note</li>
591<li>Warning</li>
592<li>Error</li>
593<li>Fatal</li>
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]594</ul>
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]595
Chris Lattner3f145382010-05-24 21:35:18 +0000[diff] [blame]596<h4 id="diagnostics_categories">Diagnostic Categories</h4>
597
598<p>Though not shown by default, diagnostics may each be associated with a
599 high-level category. This category is intended to make it possible to triage
600 builds that produce a large number of errors or warnings in a grouped way.
601</p>
602
603<p>Categories are not shown by default, but they can be turned on with the
604<a href="#opt_fdiagnostics-show-category">-fdiagnostics-show-category</a> option.
605When set to "<tt>name</tt>", the category is printed textually in the diagnostic
606output. When it is set to "<tt>id</tt>", a category number is printed. The
607mapping of category names to category id's can be obtained by running '<tt>clang
608 --print-diagnostic-categories</tt>'.
609</p>
610
611<h4 id="diagnostics_commandline">Controlling Diagnostics via Command Line
612 Flags</h4>
Chris Lattner8217f4e2009-04-20 06:26:18 +0000[diff] [blame]613
614<p>-W flags, -pedantic, etc</p>
615
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]616<h4 id="diagnostics_pragmas">Controlling Diagnostics via Pragmas</h4>
617
618<p>Clang can also control what diagnostics are enabled through the use of
619pragmas in the source code. This is useful for turning off specific warnings
620in a section of source code. Clang supports GCC's pragma for compatibility
621with existing source code, as well as several extensions. </p>
622
623<p>The pragma may control any warning that can be used from the command line.
624Warnings may be set to ignored, warning, error, or fatal. The following
625example code will tell Clang or GCC to ignore the -Wall warnings:</p>
626
627<pre>
628#pragma GCC diagnostic ignored "-Wall"
629</pre>
630
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]631<p>In addition to all of the functionality provided by GCC's pragma, Clang
Chris Lattner3401cf82009-07-12 21:22:10 +0000[diff] [blame]632also allows you to push and pop the current warning state. This is particularly
633useful when writing a header file that will be compiled by other people, because
634you don't know what warning flags they build with.</p>
635
636<p>In the below example
637-Wmultichar is ignored for only a single line of code, after which the
638diagnostics return to whatever state had previously existed.</p>
639
640<pre>
641#pragma clang diagnostic push
642#pragma clang diagnostic ignored "-Wmultichar"
643
644char b = 'df'; // no warning.
645
646#pragma clang diagnostic pop
647</pre>
648
649<p>The push and pop pragmas will save and restore the full diagnostic state of
650the compiler, regardless of how it was set. That means that it is possible to
651use push and pop around GCC compatible diagnostics and Clang will push and pop
652them appropriately, while GCC will ignore the pushes and pops as unknown
653pragmas. It should be noted that while Clang supports the GCC pragma, Clang and
654GCC do not support the exact same set of warnings, so even when using GCC
655compatible #pragmas there is no guarantee that they will have identical behaviour
656on both compilers. </p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]657
Richard Smithf122a132012-06-13 20:27:03 +0000[diff] [blame]658<h4 id="diagnostics_systemheader">Controlling Diagnostics in System Headers</h4>
659
660<p>Warnings are suppressed when they occur in system headers. By default, an
661included file is treated as a system header if it is found in an include path
662specified by <tt>-isystem</tt>, but this can be overridden in several ways.</p>
663
664<p>The <tt>system_header</tt> pragma can be used to mark the current file as
665being a system header. No warnings will be produced from the location of the
666pragma onwards within the same file.</p>
667
668<pre>
669char a = 'xy'; // warning
670
671#pragma clang system_header
672
673char b = 'ab'; // no warning
674</pre>
675
676<p>The <tt>-isystem-prefix</tt> and <tt>-ino-system-prefix</tt> command-line
677arguments can be used to override whether subsets of an include path are treated
678as system headers. When the name in a <tt>#include</tt> directive is found
679within a header search path and starts with a system prefix, the header is
680treated as a system header. The last prefix on the command-line which matches
681the specified header name takes precedence. For instance:</p>
682
683<pre>
684clang -Ifoo -isystem bar -isystem-prefix x/ -ino-system-prefix x/y/
685</pre>
686
687<p>Here, <tt>#include "x/a.h"</tt> is treated as including a system header, even
688if the header is found in <tt>foo</tt>, and <tt>#include "x/y/b.h"</tt> is
689treated as not including a system header, even if the header is found in
690<tt>bar</tt>.
691</p>
692
693<p>A <tt>#include</tt> directive which finds a file relative to the current
694directory is treated as including a system header if the including file is
695treated as a system header.</p>
696
Ted Kremenekf391fa72011-08-18 01:17:05 +0000[diff] [blame]697<h4 id="diagnostics_enable_everything">Enabling All Warnings</h4>
698
699<p>In addition to the traditional <tt>-W</tt> flags, one can enable <b>all</b>
700 warnings by passing <tt>-Weverything</tt>.
701 This works as expected with <tt>-Werror</tt>,
702 and also includes the warnings from <tt>-pedantic</tt>.</p>
703
704<p>Note that when combined with <tt>-w</tt> (which disables all warnings), that
705 flag wins.</p>
706
Ted Kremenek2fb11eb2010-08-24 18:12:35 +0000[diff] [blame]707<h4 id="analyzer_diagnositics">Controlling Static Analyzer Diagnostics</h4>
708
709<p>While not strictly part of the compiler, the diagnostics from Clang's <a
710href="http://clang-analyzer.llvm.org">static analyzer</a> can also be influenced
711by the user via changes to the source code. This can be done in two ways:
712
713<ul>
714
715<li id="analyzer_annotations"><b>Annotations</b>: The static analyzer recognizes various GCC-style
716attributes (e.g., <tt>__attribute__((nonnull)))</tt>) that can either suppress
717static analyzer warnings or teach the analyzer about code invariants which
718enable it to find more bugs. While many of these attributes are standard GCC
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]719attributes, additional ones have been added to Clang to specifically support the
Ted Kremenek2fb11eb2010-08-24 18:12:35 +0000[diff] [blame]720static analyzer. Detailed information on these annotations can be found in the
721<a href="http://clang-analyzer.llvm.org/annotations.html">analyzer's
722documentation</a>.</li>
723
724<li><b><tt>__clang_analyzer__</tt></b>: When the static analyzer is using Clang
725to parse source files, it implicitly defines the preprocessor macro
726<tt>__clang_analyzer__</tt>. While discouraged, code can use this macro to
727selectively exclude code the analyzer examines. Here is an example:
728
729<pre>
730#ifndef __clang_analyzer__
731// Code not to be analyzed
732#endif
733</pre>
734
735In general, this usage is discouraged. Instead, we prefer that users file bugs
736against the analyzer when it flags false positives. There is also active
737discussion of allowing users in the future to selectively silence specific
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]738analyzer warnings (some of which can already be done using <a
Chris Lattner2c2a3852011-12-19 07:49:23 +0000[diff] [blame]739href="#analyzer_annotations">annotations</a>).</li>
Ted Kremenek2fb11eb2010-08-24 18:12:35 +0000[diff] [blame]740
741</ul>
742
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]743<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
744<h3 id="precompiledheaders">Precompiled Headers</h3>
745<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
746
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]747<p><a href="http://en.wikipedia.org/wiki/Precompiled_header">Precompiled
748headers</a> are a general approach employed by many compilers to reduce
749compilation time. The underlying motivation of the approach is that it is
750common for the same (and often large) header files to be included by
751multiple source files. Consequently, compile times can often be greatly improved
752by caching some of the (redundant) work done by a compiler to process headers.
753Precompiled header files, which represent one of many ways to implement
754this optimization, are literally files that represent an on-disk cache that
755contains the vital information necessary to reduce some of the work
756needed to process a corresponding header file. While details of precompiled
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]757headers vary between compilers, precompiled headers have been shown to be
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]758highly effective at speeding up program compilation on systems with very large
759system headers (e.g., Mac OS/X).</p>
760
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]761<h4>Generating a PCH File</h4>
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]762
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]763<p>To generate a PCH file using Clang, one invokes Clang with
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]764the <b><tt>-x <i>&lt;language&gt;</i>-header</tt></b> option. This mirrors the
765interface in GCC for generating PCH files:</p>
766
767<pre>
768 $ gcc -x c-header test.h -o test.h.gch
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]769 $ clang -x c-header test.h -o test.h.pch
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]770</pre>
771
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]772<h4>Using a PCH File</h4>
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]773
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]774<p>A PCH file can then be used as a prefix header when a
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]775<b><tt>-include</tt></b> option is passed to <tt>clang</tt>:</p>
776
777<pre>
778 $ clang -include test.h test.c -o test
779</pre>
780
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]781<p>The <tt>clang</tt> driver will first check if a PCH file for <tt>test.h</tt>
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]782is available; if so, the contents of <tt>test.h</tt> (and the files it includes)
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]783will be processed from the PCH file. Otherwise, Clang falls back to
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]784directly processing the content of <tt>test.h</tt>. This mirrors the behavior of
785GCC.</p>
786
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]787<p><b>NOTE:</b> Clang does <em>not</em> automatically use PCH files
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]788for headers that are directly included within a source file. For example:</p>
789
790<pre>
Chris Lattnere42ec542009-06-13 20:35:58 +0000[diff] [blame]791 $ clang -x c-header test.h -o test.h.pch
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]792 $ cat test.c
793 #include "test.h"
794 $ clang test.c -o test
795</pre>
796
Douglas Gregorf4d59532009-06-03 22:37:00 +0000[diff] [blame]797<p>In this example, <tt>clang</tt> will not automatically use the PCH file for
Chris Lattner5c3074f2009-04-20 04:37:38 +0000[diff] [blame]798<tt>test.h</tt> since <tt>test.h</tt> was included directly in the source file
799and not specified on the command line using <tt>-include</tt>.</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]800
Douglas Gregore650c8c2009-07-07 00:12:59 +0000[diff] [blame]801<h4>Relocatable PCH Files</h4>
802<p>It is sometimes necessary to build a precompiled header from headers that
803are not yet in their final, installed locations. For example, one might build a
804precompiled header within the build tree that is then meant to be installed
805alongside the headers. Clang permits the creation of "relocatable" precompiled
806headers, which are built with a given path (into the build directory) and can
807later be used from an installed location.</p>
808
809<p>To build a relocatable precompiled header, place your headers into a
810subdirectory whose structure mimics the installed location. For example, if you
811want to build a precompiled header for the header <code>mylib.h</code> that
812will be installed into <code>/usr/include</code>, create a subdirectory
813<code>build/usr/include</code> and place the header <code>mylib.h</code> into
814that subdirectory. If <code>mylib.h</code> depends on other headers, then
815they can be stored within <code>build/usr/include</code> in a way that mimics
816the installed location.</p>
817
818<p>Building a relocatable precompiled header requires two additional arguments.
819First, pass the <code>--relocatable-pch</code> flag to indicate that the
820resulting PCH file should be relocatable. Second, pass
821<code>-isysroot /path/to/build</code>, which makes all includes for your
822library relative to the build directory. For example:</p>
823
824<pre>
825 # clang -x c-header --relocatable-pch -isysroot /path/to/build /path/to/build/mylib.h mylib.h.pch
826</pre>
827
828<p>When loading the relocatable PCH file, the various headers used in the PCH
829file are found from the system header root. For example, <code>mylib.h</code>
830can be found in <code>/usr/include/mylib.h</code>. If the headers are installed
831in some other system root, the <code>-isysroot</code> option can be used provide
832a different system root from which the headers will be based. For example,
833<code>-isysroot /Developer/SDKs/MacOSX10.4u.sdk</code> will look for
834<code>mylib.h</code> in
835<code>/Developer/SDKs/MacOSX10.4u.sdk/usr/include/mylib.h</code>.</p>
836
837<p>Relocatable precompiled headers are intended to be used in a limited number
838of cases where the compilation environment is tightly controlled and the
839precompiled header cannot be generated after headers have been installed.
840Relocatable precompiled headers also have some performance impact, because
841the difference in location between the header locations at PCH build time vs.
842at the time of PCH use requires one of the PCH optimizations,
843<code>stat()</code> caching, to be disabled. However, this change is only
844likely to affect PCH files that reference a large number of headers.</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]845
Mike Stump53664ca2009-12-14 23:53:10 +0000[diff] [blame]846<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
847<h3 id="codegen">Controlling Code Generation</h3>
848<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
849
850<p>Clang provides a number of ways to control code generation. The options are listed below.</p>
851
852<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]853<dl>
Mike Stump53664ca2009-12-14 23:53:10 +0000[diff] [blame]854<dt id="opt_fcatch-undefined-behavior"><b>-fcatch-undefined-behavior</b>: Turn
855on runtime code generation to check for undefined behavior.</dt>
856
857<dd>This option, which defaults to off, controls whether or not Clang
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]858adds runtime checks for undefined runtime behavior. If a check fails,
Mike Stump53664ca2009-12-14 23:53:10 +0000[diff] [blame]859<tt>__builtin_trap()</tt> is used to indicate failure.
860The checks are:
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]861<ul>
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]862<li>Subscripting where the static type of one operand is a variable
Mike Stump88b2a172009-12-16 03:25:12 +0000[diff] [blame]863 which is decayed from an array type and the other operand is
864 greater than the size of the array or less than zero.</li>
Mike Stump53664ca2009-12-14 23:53:10 +0000[diff] [blame]865<li>Shift operators where the amount shifted is greater or equal to the
866 promoted bit-width of the left-hand-side or less than zero.</li>
Mike Stump8f6a3ed2009-12-16 03:18:14 +0000[diff] [blame]867<li>If control flow reaches __builtin_unreachable.
868<li>When llvm implements more __builtin_object_size support, reads and
869 writes for objects that __builtin_object_size indicates we aren't
870 accessing valid memory. Bit-fields and vectors are not yet checked.
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]871</ul>
Mike Stump53664ca2009-12-14 23:53:10 +0000[diff] [blame]872</dd>
873
Kostya Serebryany48a8cd92012-03-01 23:14:19 +0000[diff] [blame]874<dt id="opt_faddress-sanitizer"><b>-f[no-]address-sanitizer</b>:
875Turn on <a href="AddressSanitizer.html">AddressSanitizer</a>,
876a memory error detector.
877
878<dt id="opt_fthread-sanitizer"><b>-f[no-]thread-sanitizer</b>:
879Turn on ThreadSanitizer, an <em>experimental</em> data race detector.
880Not ready for widespread use.
881
Nuno Lopesaa526242009-12-17 10:00:52 +0000[diff] [blame]882<dt id="opt_fno-assume-sane-operator-new"><b>-fno-assume-sane-operator-new</b>:
883Don't assume that the C++'s new operator is sane.</dt>
Nuno Lopesb23f20d2009-12-17 10:15:49 +0000[diff] [blame]884<dd>This option tells the compiler to do not assume that C++'s global new
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]885operator will always return a pointer that does not
Nuno Lopesaa526242009-12-17 10:00:52 +0000[diff] [blame]886alias any other pointer when the function returns.</dd>
Evan Chengfda026b2011-04-08 22:18:01 +0000[diff] [blame]887
Evan Cheng4cf4b592011-04-08 22:34:21 +0000[diff] [blame]888<dt id="opt_ftrap-function"><b>-ftrap-function=[name]</b>: Instruct code
Evan Chengfda026b2011-04-08 22:18:01 +0000[diff] [blame]889generator to emit a function call to the specified function name for
890<tt>__builtin_trap()</tt>.</dt>
891
892<dd>LLVM code generator translates <tt>__builtin_trap()</tt> to a trap
893instruction if it is supported by the target ISA. Otherwise, the builtin is
894translated into a call to <tt>abort</tt>. If this option is set, then the code
895generator will always lower the builtin to a call to the specified function
896regardless of whether the target ISA has a trap instruction. This option is
Chris Lattner02e266b2011-04-08 22:58:43 +0000[diff] [blame]897useful for environments (e.g. deeply embedded) where a trap cannot be properly
898handled, or when some custom behavior is desired.</dd>
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]899</dl>
Nuno Lopesaa526242009-12-17 10:00:52 +0000[diff] [blame]900
Alexey Samsonov5ab52492012-05-30 06:55:10 +0000[diff] [blame]901<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
902<h3 id="debuginfosize">Controlling Size of Debug Information</h3>
903<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
904
905<p>Debug info kind generated by Clang can be set by one of the flags listed
906below. If multiple flags are present, the last one is used.</p>
907
908<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
909<dl>
910<dt id="opt_g0"><b>-g0</b>: Don't generate any debug info (default).
911
912<dt id="opt_gline-tables-only"><b>-gline-tables-only</b>:
913Generate line number tables only.
914<dd>
915This kind of debug info allows to obtain stack traces with function
916names, file names and line numbers (by such tools as
917gdb or addr2line). It doesn't contain any other data (e.g.
918description of local variables or function parameters).
919</dd>
920
921<dt id="opt_g"><b>-g</b>: Generate complete debug info.
922</dl>
923
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]924<!-- ======================================================================= -->
925<h2 id="c">C Language Features</h2>
926<!-- ======================================================================= -->
927
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]928<p>The support for standard C in clang is feature-complete except for the C99
929floating-point pragmas.</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]930
931<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]932<h3 id="c_ext">Extensions supported by clang</h3>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]933<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
934
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]935<p>See <a href="LanguageExtensions.html">clang language extensions</a>.</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]936
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]937<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
938<h3 id="c_modes">Differences between various standard modes</h3>
939<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]940
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]941<p>clang supports the -std option, which changes what language mode clang uses.
942The supported modes for C are c89, gnu89, c94, c99, gnu99 and various aliases
943for those modes. If no -std option is specified, clang defaults to gnu99 mode.
944</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]945
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]946<p>Differences between all c* and gnu* modes:</p>
947<ul>
948<li>c* modes define "__STRICT_ANSI__".</li>
Eli Friedman26fa0ed2009-05-27 23:02:57 +0000[diff] [blame]949<li>Target-specific defines not prefixed by underscores, like "linux", are
950defined in gnu* modes.</li>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]951<li>Trigraphs default to being off in gnu* modes; they can be enabled by the
952-trigraphs option.</li>
953<li>The parser recognizes "asm" and "typeof" as keywords in gnu* modes; the
954variants "__asm__" and "__typeof__" are recognized in all modes.</li>
Eli Friedmanb0ac5452009-05-16 23:17:30 +0000[diff] [blame]955<li>The Apple "blocks" extension is recognized by default in gnu* modes
956on some platforms; it can be enabled in any mode with the "-fblocks"
957option.</li>
Chris Lattner741be6a2011-06-15 00:41:40 +0000[diff] [blame]958<li>Arrays that are VLA's according to the standard, but which can be constant
959 folded by the frontend are treated as fixed size arrays. This occurs for
960 things like "int X[(1, 2)];", which is technically a VLA. c* modes are
961 strictly compliant and treat these as VLAs.</li>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]962</ul>
963
964<p>Differences between *89 and *99 modes:</p>
965<ul>
966<li>The *99 modes default to implementing "inline" as specified in C99, while
967the *89 modes implement the GNU version. This can be overridden for individual
968functions with the __gnu_inline__ attribute.</li>
Eli Friedman26fa0ed2009-05-27 23:02:57 +0000[diff] [blame]969<li>Digraphs are not recognized in c89 mode.</li>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]970<li>The scope of names defined inside a "for", "if", "switch", "while", or "do"
971statement is different. (example: "if ((struct x {int x;}*)0) {}".)</li>
972<li>__STDC_VERSION__ is not defined in *89 modes.</li>
Eli Friedman26fa0ed2009-05-27 23:02:57 +0000[diff] [blame]973<li>"inline" is not recognized as a keyword in c89 mode.</li>
974<li>"restrict" is not recognized as a keyword in *89 modes.</li>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]975<li>Commas are allowed in integer constant expressions in *99 modes.</li>
976<li>Arrays which are not lvalues are not implicitly promoted to pointers in
977*89 modes.</li>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]978<li>Some warnings are different.</li>
979</ul>
980
981<p>c94 mode is identical to c89 mode except that digraphs are enabled in
982c94 mode (FIXME: And __STDC_VERSION__ should be defined!).</p>
983
984<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
985<h3 id="c_unimpl_gcc">GCC extensions not implemented yet</h3>
986<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
987
988<p>clang tries to be compatible with gcc as much as possible, but some gcc
989extensions are not implemented yet:</p>
990
991<ul>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]992
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]993<li>clang does not support #pragma weak
Eli Friedman4da92552009-06-02 08:21:31 +0000[diff] [blame]994(<a href="http://llvm.org/bugs/show_bug.cgi?id=3679">bug 3679</a>). Due to
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]995the uses described in the bug, this is likely to be implemented at some
996point, at least partially.</li>
997
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]998<li>clang does not support decimal floating point types (_Decimal32 and
999friends) or fixed-point types (_Fract and friends); nobody has expressed
1000interest in these features yet, so it's hard to say when they will be
1001implemented.</li>
1002
1003<li>clang does not support nested functions; this is a complex feature which
1004is infrequently used, so it is unlikely to be implemented anytime soon.</li>
1005
Daniel Dunbar05fa6292009-05-12 23:12:07 +0000[diff] [blame]1006<li>clang does not support global register variables, this is unlikely
Eli Friedmanca130bd2009-06-12 20:04:25 +0000[diff] [blame]1007to be implemented soon because it requires additional LLVM backend support.
1008</li>
Daniel Dunbar05fa6292009-05-12 23:12:07 +0000[diff] [blame]1009
1010<li>clang does not support static initialization of flexible array
1011members. This appears to be a rarely used extension, but could be
1012implemented pending user demand.</li>
1013
Eli Friedmanca130bd2009-06-12 20:04:25 +0000[diff] [blame]1014<li>clang does not support __builtin_va_arg_pack/__builtin_va_arg_pack_len.
1015This is used rarely, but in some potentially interesting places, like the
1016glibc headers, so it may be implemented pending user demand. Note that
1017because clang pretends to be like GCC 4.2, and this extension was introduced
1018in 4.3, the glibc headers will not try to use this extension with clang at
1019the moment.</li>
1020
1021<li>clang does not support the gcc extension for forward-declaring function
1022parameters; this has not showed up in any real-world code yet, though, so it
1023might never be implemented.</li>
1024
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]1025</ul>
1026
1027<p>This is not a complete list; if you find an unsupported extension
1028missing from this list, please send an e-mail to cfe-dev. This list
1029currently excludes C++; see <a href="#cxx">C++ Language Features</a>.
1030Also, this list does not include bugs in mostly-implemented features; please
1031see the <a href="http://llvm.org/bugs/buglist.cgi?quicksearch=product%3Aclang+component%3A-New%2BBugs%2CAST%2CBasic%2CDriver%2CHeaders%2CLLVM%2BCodeGen%2Cparser%2Cpreprocessor%2CSemantic%2BAnalyzer">
1032bug tracker</a> for known existing bugs (FIXME: Is there a section for
1033bug-reporting guidelines somewhere?).</p>
1034
1035<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1036<h3 id="c_unsupp_gcc">Intentionally unsupported GCC extensions</h3>
1037<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1038
Eli Friedman0b326002009-06-12 20:11:05 +0000[diff] [blame]1039<ul>
1040
Eli Friedman2f3fca02009-06-12 20:08:48 +0000[diff] [blame]1041<li>clang does not support the gcc extension that allows variable-length arrays
Chris Lattnerd462b6a2011-01-24 03:47:59 +0000[diff] [blame]1042in structures. This is for a few reasons: one, it is tricky
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]1043to implement, two, the extension is completely undocumented, and three, the
Chris Lattnerb9d511c2010-10-28 02:20:32 +0000[diff] [blame]1044extension appears to be rarely used. Note that clang <em>does</em> support
1045flexible array members (arrays with a zero or unspecified size at the end of
1046a structure).</li>
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]1047
Eli Friedmanca130bd2009-06-12 20:04:25 +0000[diff] [blame]1048<li>clang does not have an equivalent to gcc's "fold"; this means that
1049clang doesn't accept some constructs gcc might accept in contexts where a
Eli Friedman248f9732011-06-13 23:12:01 +0000[diff] [blame]1050constant expression is required, like "x-x" where x is a variable.</li>
Eli Friedmanca130bd2009-06-12 20:04:25 +0000[diff] [blame]1051
Eli Friedmanca130bd2009-06-12 20:04:25 +0000[diff] [blame]1052<li>clang does not support __builtin_apply and friends; this extension is
1053extremely obscure and difficult to implement reliably.</li>
1054
Eli Friedman0b326002009-06-12 20:11:05 +0000[diff] [blame]1055</ul>
1056
Eli Friedman660a5ac2009-04-28 18:48:34 +0000[diff] [blame]1057<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1058<h3 id="c_ms">Microsoft extensions</h3>
1059<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1060
1061<p>clang has some experimental support for extensions from
1062Microsoft Visual C++; to enable it, use the -fms-extensions command-line
Eli Friedmana1821b52009-06-08 06:21:03 +0000[diff] [blame]1063option. This is the default for Windows targets. Note that the
1064support is incomplete; enabling Microsoft extensions will silently drop
1065certain constructs (including __declspec and Microsoft-style asm statements).
1066</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]1067
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]1068<ul>
Douglas Gregord3b227d2010-12-14 16:21:49 +0000[diff] [blame]1069<li>clang allows setting _MSC_VER with -fmsc-version=. It defaults to 1300 which
Michael J. Spencerdae4ac42010-10-21 05:21:48 +0000[diff] [blame]1070is the same as Visual C/C++ 2003. Any number is supported and can greatly affect
1071what Windows SDK and c++stdlib headers clang can compile. This option will be
1072removed when clang supports the full set of MS extensions required for these
1073headers.</li>
1074
Daniel Dunbar05fa6292009-05-12 23:12:07 +0000[diff] [blame]1075<li>clang does not support the Microsoft extension where anonymous
Daniel Dunbar869e0542009-05-13 00:23:53 +0000[diff] [blame]1076record members can be declared using user defined typedefs.</li>
Daniel Dunbar05fa6292009-05-12 23:12:07 +0000[diff] [blame]1077
Daniel Dunbar9375ed12009-05-13 21:40:49 +0000[diff] [blame]1078<li>clang supports the Microsoft "#pragma pack" feature for
1079controlling record layout. GCC also contains support for this feature,
1080however where MSVC and GCC are incompatible clang follows the MSVC
1081definition.</li>
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]1082</ul>
Daniel Dunbar9375ed12009-05-13 21:40:49 +0000[diff] [blame]1083
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]1084<!-- ======================================================================= -->
Richard Smithbdb10182011-11-21 20:54:59 +0000[diff] [blame]1085<h2 id="cxx">C++ Language Features</h2>
1086<!-- ======================================================================= -->
1087
1088<p>clang fully implements all of standard C++98 except for exported templates
1089(which were removed in C++11), and
1090<a href="http://clang.llvm.org/cxx_status.html">many C++11 features</a> are also
1091implemented.</p>
1092
1093<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1094<h3 id="cxx_implimits">Controlling implementation limits</h3>
1095<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1096
1097<p><b>-fconstexpr-depth=N</b>: Sets the limit for recursive constexpr function
1098invocations to N. The default is 512.</p>
1099
1100<p><b>-ftemplate-depth=N</b>: Sets the limit for recursively nested template
1101instantiations to N. The default is 1024.</p>
1102
1103<!-- ======================================================================= -->
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]1104<h2 id="target_features">Target-Specific Features and Limitations</h2>
1105<!-- ======================================================================= -->
1106
1107
1108<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1109<h3 id="target_arch">CPU Architectures Features and Limitations</h3>
1110<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1111
1112<!-- ======================== -->
1113<h4 id="target_arch_x86">X86</h4>
1114<!-- ======================== -->
Daniel Dunbarbcaf7aa2010-09-19 19:26:59 +0000[diff] [blame]1115
1116<p>The support for X86 (both 32-bit and 64-bit) is considered stable on Darwin
1117(Mac OS/X), Linux, FreeBSD, and Dragonfly BSD: it has been tested to correctly
1118compile many large C, C++, Objective-C, and Objective-C++ codebases.</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]1119
NAKAMURA Takumiddf68ff2011-04-05 04:31:31 +0000[diff] [blame]1120<p>On x86_64-mingw32, passing i128(by value) is incompatible to Microsoft x64
1121calling conversion. You might need to tweak WinX86_64ABIInfo::classify()
1122in lib/CodeGen/TargetInfo.cpp.</p>
NAKAMURA Takumia75fdb22011-04-04 15:02:41 +0000[diff] [blame]1123
Eli Friedman3b658d32009-06-08 05:12:39 +0000[diff] [blame]1124<!-- ======================== -->
1125<h4 id="target_arch_arm">ARM</h4>
1126<!-- ======================== -->
Daniel Dunbarbcaf7aa2010-09-19 19:26:59 +0000[diff] [blame]1127
1128<p>The support for ARM (specifically ARMv6 and ARMv7) is considered stable on
1129Darwin (iOS): it has been tested to correctly compile many large C, C++,
Bob Wilson4ea8dfa2011-01-10 17:55:14 +0000[diff] [blame]1130Objective-C, and Objective-C++ codebases. Clang only supports a limited number
1131of ARM architectures. It does not yet fully support ARMv5, for example.</p>
Eli Friedman3b658d32009-06-08 05:12:39 +0000[diff] [blame]1132
1133<!-- ======================== -->
1134<h4 id="target_arch_other">Other platforms</h4>
1135<!-- ======================== -->
1136clang currently contains some support for PPC and Sparc; however, significant
1137pieces of code generation are still missing, and they haven't undergone
1138significant testing.
1139
Eli Friedman3b658d32009-06-08 05:12:39 +0000[diff] [blame]1140<p>clang contains limited support for the MSP430 embedded processor, but both
1141the clang support and the LLVM backend support are highly experimental.
1142
1143<p>Other platforms are completely unsupported at the moment. Adding the
1144minimal support needed for parsing and semantic analysis on a new platform
1145is quite easy; see lib/Basic/Targets.cpp in the clang source tree. This level
1146of support is also sufficient for conversion to LLVM IR for simple programs.
1147Proper support for conversion to LLVM IR requires adding code to
1148lib/CodeGen/CGCall.cpp at the moment; this is likely to change soon, though.
1149Generating assembly requires a suitable LLVM backend.
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]1150
1151<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1152<h3 id="target_os">Operating System Features and Limitations</h3>
1153<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
1154
1155<!-- ======================================= -->
1156<h4 id="target_os_darwin">Darwin (Mac OS/X)</h4>
1157<!-- ======================================= -->
1158
Chris Lattner396663b2012-05-04 21:11:08 +0000[diff] [blame]1159<p>None</p>
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]1160
NAKAMURA Takumia75fdb22011-04-04 15:02:41 +0000[diff] [blame]1161<!-- ======================================= -->
1162<h4 id="target_os_win32">Windows</h4>
1163<!-- ======================================= -->
1164
1165<p>Experimental supports are on Cygming.</p>
1166
1167<h5>Cygwin</h5>
1168
1169<p>Clang works on Cygwin-1.7.</p>
1170
1171<h5>MinGW32</h5>
1172
1173<p>Clang works on some mingw32 distributions.
1174Clang assumes directories as below;</p>
1175
1176<ul>
1177<li><tt>C:/mingw/include</tt></li>
1178<li><tt>C:/mingw/lib</tt></li>
1179<li><tt>C:/mingw/lib/gcc/mingw32/4.[3-5].0/include/c++</tt></li>
1180</ul>
1181
NAKAMURA Takumi0e53df62011-11-17 07:54:13 +0000[diff] [blame]1182<p>On MSYS, a few tests might fail.</p>
NAKAMURA Takumia75fdb22011-04-04 15:02:41 +0000[diff] [blame]1183
1184<h5>MinGW-w64</h5>
1185
Douglas Gregordad879a2011-08-30 00:40:12 +0000[diff] [blame]1186<p>For 32-bit (i686-w64-mingw32), and 64-bit (x86_64-w64-mingw32), Clang assumes as below;<p>
NAKAMURA Takumia75fdb22011-04-04 15:02:41 +0000[diff] [blame]1187
1188<ul>
Douglas Gregordad879a2011-08-30 00:40:12 +0000[diff] [blame]1189<li><tt>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)</tt></li>
1190<li><tt>some_directory/bin/gcc.exe</tt></li>
1191<li><tt>some_directory/bin/clang.exe</tt></li>
1192<li><tt>some_directory/bin/clang++.exe</tt></li>
1193<li><tt>some_directory/bin/../include/c++/GCC_version</tt></li>
1194<li><tt>some_directory/bin/../include/c++/GCC_version/x86_64-w64-mingw32</tt></li>
1195<li><tt>some_directory/bin/../include/c++/GCC_version/i686-w64-mingw32</tt></li>
1196<li><tt>some_directory/bin/../include/c++/GCC_version/backward</tt></li>
1197<li><tt>some_directory/bin/../x86_64-w64-mingw32/include</tt></li>
1198<li><tt>some_directory/bin/../i686-w64-mingw32/include</tt></li>
1199<li><tt>some_directory/bin/../include</tt></li>
NAKAMURA Takumia75fdb22011-04-04 15:02:41 +0000[diff] [blame]1200</ul>
1201
David Blaikiea9639622012-04-19 17:21:46 +0000[diff] [blame]1202<p>This directory layout is standard for any toolchain you will find on the official <a href="http://mingw-w64.sourceforge.net">MinGW-w64 website</a>.
Douglas Gregordad879a2011-08-30 00:40:12 +0000[diff] [blame]1203
1204<p>Clang expects the GCC executable &quot;gcc.exe&quot; compiled for i686-w64-mingw32 (or x86_64-w64-mingw32) to be present on PATH.</p>
1205
1206<p><a href="http://llvm.org/bugs/show_bug.cgi?id=9072">Some tests might fail</a>
1207on x86_64-w64-mingw32.</p>
NAKAMURA Takumia75fdb22011-04-04 15:02:41 +0000[diff] [blame]1208
Chris Lattnercf17d9d2009-04-20 04:23:09 +0000[diff] [blame]1209</div>
1210</body>
1211</html>