1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
|
<html>
<head>
<title>Clang 3.0 Release Notes</title>
<link type="text/css" rel="stylesheet" href="../menu.css" />
<link type="text/css" rel="stylesheet" href="../content.css" />
<style type="text/css">
td {
vertical-align: top;
}
</style>
</head>
<body>
<!--#include virtual="../menu.html.incl"-->
<div id="content">
<h1>Clang 3.0 Release Notes</h1>
<img align=right src="http://llvm.org/img/DragonSmall.png"
width="136" height="136" alt="LLVM Dragon Logo">
<ul>
<li><a href="#intro">Introduction</a></li>
<li><a href="#whatsnew">What's New in Clang 3.0?</a>
<ul>
<li><a href="#majorfeatures">Major New Features</a></li>
<li><a href="#cchanges">C Language Changes</a></li>
<li><a href="#cxxhanges">C++ Language Changes</a></li>
<li><a href="#objchanges">Objective-C Language Changes</a></li>
<li><a href="#apichanges">Internal API Changes</a></li>
</li>
<li><a href="#knownproblems">Known Problems</a></li>
<li><a href="#additionalinfo">Additional Information</a></li>
</ul>
<div class="doc_author">
<p>Written by the <a href="http://llvm.org/">LLVM Team</a></p>
</div>
<!--
<h1 style="color:red">These are in-progress notes for the upcoming LLVM 3.0
release.<br>
You may prefer the
<a href="http://llvm.org/releases/2.9/docs/ReleaseNotes.html">LLVM 2.9
Release Notes</a>.</h1>
-->
<!-- ======================================================================= -->
<h2 id="intro">Introduction</h2>
<!-- ======================================================================= -->
<p>This document contains the release notes for the Clang C/C++/Objective-C
frontend, part of the LLVM Compiler Infrastructure, release 3.0. Here we
describe the status of Clang in some detail, including major improvements from
the previous release and new feature work. For the general LLVM release notes,
see <a href ="http;//llvm.org/docs/ReleaseNotes.html">the LLVM
documentation</a>. All LLVM releases may be downloaded from the
<a href="http://llvm.org/releases/">LLVM releases web site</a>.</p>
<p>For more information about Clang or LLVM, including information about the
latest release, please check out the main please see the
<a href="http://clang.llvm.org">Clang Web Site</a> or the
<a href="http://llvm.org">LLVM Web Site</a>.
<p>Note that if you are reading this file from a Subversion checkout or the main
Clang web page, this document applies to the <i>next</i> release, not the
current one. To see the release notes for a specific release, please see the
<a href="http://llvm.org/releases/">releases page</a>.</p>
<!-- ======================================================================= -->
<h2 id="whatsnew">What's New in Clang 3.0?</h2>
<!-- ======================================================================= -->
<p>Some of the major new features and improvements to Clang are listed here.
Generic improvements to Clang as a whole or two its underlying infrastructure
are described first, followed by language-specific sections with improvements to
Clang's support for those languages.</p>
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<h3 id="majorfeatures">Major New Features</h3>
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<h4 id="notes">Unorganized Notes</h4>
<p>These are completely random notes as I'm organizing my thoughts and reviewing
the history. Anything still here needs to be distilled and turned into proper
prose in a section of its own. When doing that, delete the notes.</p>
<ul>
<li>Make analyzer (especially as used w/ warnings in Clang) much faster</li>
<li>OpenCL support -- need details from Tanya and Peter -- separate language
section?</li>
<li>Building Clang on windows -- mingw, 32 and 64 bit, native windows builds,
cygwin. get chapuni to flesh out details.</li>
<li>Compiling C/C++ w/ MinGW (32/64) and Cygwin on Windows -- chapuni</li>
<li>C++ -- Parsing and AST support for Windows Structured Exception
Handling.</li>
<li>C++11 -- noexcept (Sebastian Redl)</li>
<li>Uninitialized values Clang warning rewrite -- more accurate, faster, able
to differentiate between the possibility of an uninitialized use and the
certainty of an uninitialized use.</li>
<li>Enhancements to PPCallbacks
<ul>
<li>exact include paths</li>
<li>source range for macro expansions</li>
</ul>
</li>
<li>Support for language specific address spaces</li>
<li>Support for compiling on NetBSD systems -- Joerg Sonnenberger to fill
out</li>
<li>Support for '--sysroot' based cross-compilation</li>
<li>Crash recovery handling for libclang clients -- Ted</li>
<li>Driver support for automatic preparation of reproduction steps for
compiler crashes -- Chad</li>
<li>OS Availability attribute -- r128127</li>
<li>GNU ObjectiveC Runtime support -- David Chisnall</li>
<li>C++11 -- override</li>
<li>Diagnostic improvements bucket?
<ul>
<li>Emitting fewer include stacks</li>
<li>Significantly better recovery when encountering misspelled type names
in a declaration context. r130082</li>
<li>Expanded typo correction, most especially namespace-aware typo
correction in C++</li>
<li>Significantly more rich diagnostics w.r.t. macro expansion backtraces,
especially when macro arguments are involved.</li>
</ul>
</li>
<li>libclang improvements bucket
<ul>
<li>Better Python Bindings</li>
<li>More AST coverage</li>
<li>Improved cursor support within macros, especially function-style macro
arguments.</li>
<li>Improved code completion surrounding macros, macro arguments, and
token pasting.</li>
<li>Improved code completion for in-class member functions.</li>
</ul>
</li>
<li>C++ -- supported in the static analyzer: methods, new, constructors,
destructors, etc.</li>
<li>Improved AST support for partially constructed nodes and incomplete
information for LLDB and other clients which dynamically build AST nodes.</li>
<li>Largely complete MSVC-compatible parsing mode -- fpichet</li>
<li>C1X -- static asserts and generic selections</li>
<li>C++11 -- alias declarations -- zygoloid</li>
<li>C++11 -- range-based-for loops -- zygoloid</li>
<li>C++11 -- nullptr -- zygoloid</li>
<li>C++11 -- in-class init -- zygoloid</li>
<li>C++11 -- raw string literals -- zygoloid</li>
<li>C++11 -- delegating ctors -- zygoloid/scshunt</li>
<li>Memory reduction -- initializers, macro expansions, source locations,
etc.</li>
<li>Full set of type traits, sufficient to support C++11 standard libraries;
also expression traits.</li>
<li>CFI-based debug info -- nlewycky/espindola details</li>
<li>ObjC ARC -- get a blurb from rjmccall</li>
<li>ObjC related result type/instancetype</li>
<li>API -- The term "instantiation" w.r.t. macros in APIs has been completely
replaced by the term "expansion".</li>
<li>Thread Safety attributes and correctness analysis added to Clang.</li>
<li>API -- Many opaque typedefs in Sema around AST nodes are gone.</li>
<li>NRVO for blocks.</li>
<li>Major improvements to the interactions between serializing and
deserializing the AST and the preprocessor -- argiris</li>
<li>API -- Diagnostics API shuffle:
<ul>
<li>Diagnostic became DiagnosticEngine</li>
<li>DiagnosticClient became DiagnosticConsumer</li>
<li>DiagnosticInfo became Diagnostic</li>
</ul>
</li>
<li>Major driver and system compatibility changes:
<ul>
<li>Correct support for many more hardware architecture pre-defined macros
(e.g., __i686__).</li>
<li>Much more robust detection of library and header search paths on Linux
distributions.</li>
<li>Partial support for sysroot based cross compiling on Linux (like)
systems.</li>
<li>Improved support for locating and using libcxx, especially on
Darwin.</li>
</ul>
</li>
<li>Initial steps of CUDA support -- Peter</li>
<li>Atomic builtins and C1X specifiers using the new LLVM atomic instructions
and memory model -- efriedma, jyasskin</li>
</ul>
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<h3 id="cchanges">C Language Changes in Clang</h3>
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<h3 id="cxxchanges">C++ Language Changes in Clang</h3>
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<h3 id="objcchanges">Objective-C Language Changes in Clang</h3>
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<h3 id="apichanges">Internal API Changes</h3>
<!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
<!-- ======================================================================= -->
<h2 id="knownproblems">Significant Known Problems</h2>
<!-- ======================================================================= -->
<!-- ======================================================================= -->
<h2 id="additionalinfo">Additional Information</h2>
<!-- ======================================================================= -->
<p>A wide variety of additional information is available on the
<a href="http://clang.llvm.org/">Clang web page</a>. The web page contains
versions of the API documentation which are up-to-date with the Subversion
version of the source code. You can access versions of these documents specific
to this release by going into the "<tt>clang/doc/</tt>" directory in the Clang
tree.</p>
<p>If you have any questions or comments about Clang, please feel free to
contact us via the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">
mailing list</a>.</p>
</body>
</html>
|