1 =====================================
2 Clang 3.7 (In-Progress) Release Notes
3 =====================================
9 Written by the `LLVM Team <http://llvm.org/>`_
13 These are in-progress notes for the upcoming Clang 3.7 release. You may
14 prefer the `Clang 3.6 Release Notes
15 <http://llvm.org/releases/3.6.0/tools/clang/docs/ReleaseNotes.html>`_.
20 This document contains the release notes for the Clang C/C++/Objective-C
21 frontend, part of the LLVM Compiler Infrastructure, release 3.7. Here we
22 describe the status of Clang in some detail, including major
23 improvements from the previous release and new feature work. For the
24 general LLVM release notes, see `the LLVM
25 documentation <http://llvm.org/docs/ReleaseNotes.html>`_. All LLVM
26 releases may be downloaded from the `LLVM releases web
27 site <http://llvm.org/releases/>`_.
29 For more information about Clang or LLVM, including information about
30 the latest release, please check out the main please see the `Clang Web
31 Site <http://clang.llvm.org>`_ or the `LLVM Web
32 Site <http://llvm.org>`_.
34 Note that if you are reading this file from a Subversion checkout or the
35 main Clang web page, this document applies to the *next* release, not
36 the current one. To see the release notes for a specific release, please
37 see the `releases page <http://llvm.org/releases/>`_.
39 What's New in Clang 3.7?
40 ========================
42 Some of the major new features and improvements to Clang are listed
43 here. Generic improvements to Clang as a whole or to its underlying
44 infrastructure are described first, followed by language-specific
45 sections with improvements to Clang's support for those languages.
50 - Use of the ``__declspec`` language extension for declaration attributes now
51 requires passing the -fms-extensions or -fborland compiler flag. This language
52 extension is also enabled when compiling CUDA code, but its use should be
53 viewed as an implementation detail that is subject to change.
55 Improvements to Clang's diagnostics
56 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
58 Clang's diagnostics are constantly being improved to catch more issues,
59 explain them more clearly, and provide more accurate source information
60 about them. The improvements since the 3.5 release include:
67 The sized deallocation feature of C++14 is now controlled by the
68 ``-fsized-deallocation`` flag. This feature relies on library support that
69 isn't yet widely deployed, so the user must supply an extra flag to get the
76 -----------------------
78 Clang now supports the ...
83 Clang's support for building native Windows programs ...
86 C Language Changes in Clang
87 ---------------------------
96 C++ Language Changes in Clang
97 -----------------------------
101 C++11 Feature Support
102 ^^^^^^^^^^^^^^^^^^^^^
106 Objective-C Language Changes in Clang
107 -------------------------------------
111 OpenCL C Language Changes in Clang
112 ----------------------------------
119 These are major API changes that have happened since the 3.6 release of
120 Clang. If upgrading an external codebase that uses Clang as a library,
121 this section should help get you past the largest hurdles of upgrading.
123 - Some of the `PPCallbacks` interface now deals in `MacroDefinition`
124 objects instead of `MacroDirective` objects. This allows preserving
125 full information on macros imported from modules.
127 - `clang-c/Index.h` no longer `#include`\s `clang-c/Documentation.h`.
128 You now need to explicitly `#include "clang-c/Documentation.h"` if
129 you use the libclang documentation API.
141 Core Analysis Improvements
142 ==========================
151 Python Binding Changes
152 ----------------------
154 The following methods have been added:
158 Significant Known Problems
159 ==========================
161 Additional Information
162 ======================
164 A wide variety of additional information is available on the `Clang web
165 page <http://clang.llvm.org/>`_. The web page contains versions of the
166 API documentation which are up-to-date with the Subversion version of
167 the source code. You can access versions of these documents specific to
168 this release by going into the "``clang/docs/``" directory in the Clang
171 If you have any questions or comments about Clang, please feel free to
172 contact us via the `mailing
173 list <http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev>`_.