r216293 - Clear the clang release notes to make room for 3.6.
rafael.espindola at gmail.com
Fri Aug 22 14:59:11 PDT 2014
Date: Fri Aug 22 16:59:11 2014
New Revision: 216293
Clear the clang release notes to make room for 3.6.
--- cfe/trunk/docs/ReleaseNotes.rst (original)
+++ cfe/trunk/docs/ReleaseNotes.rst Fri Aug 22 16:59:11 2014
@@ -10,15 +10,15 @@ Written by the `LLVM Team <http://llvm.o
- These are in-progress notes for the upcoming Clang 3.5 release. You may
- prefer the `Clang 3.4 Release Notes
+ These are in-progress notes for the upcoming Clang 3.6 release. You may
+ prefer the `Clang 3.5 Release Notes
This document contains the release notes for the Clang C/C++/Objective-C
-frontend, part of the LLVM Compiler Infrastructure, release 3.5. Here we
+frontend, part of the LLVM Compiler Infrastructure, release 3.6. 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 `the LLVM
@@ -36,7 +36,7 @@ main Clang web page, this document appli
the current one. To see the release notes for a specific release, please
see the `releases page <http://llvm.org/releases/>`_.
-What's New in Clang 3.5?
+What's New in Clang 3.6?
Some of the major new features and improvements to Clang are listed
@@ -47,14 +47,7 @@ sections with improvements to Clang's su
Major New Features
-- Clang uses the new MingW ABI
- GCC 4.7 changed the mingw ABI. Clang 3.4 and older use the GCC 4.6
- ABI. Clang 3.5 and newer use the GCC 4.7 abi.
-- The __has_attribute feature test is now target-aware. Older versions of Clang
- would return true when the attribute spelling was known, regardless of whether
- the attribute was available to the specific target. Clang now returns true
- only when the attribute pertains to the current compilation target.
+- A big one.
Improvements to Clang's diagnostics
@@ -62,77 +55,25 @@ Improvements to Clang's diagnostics
Clang's diagnostics are constantly being improved to catch more issues,
explain them more clearly, and provide more accurate source information
-about them. The improvements since the 3.4 release include:
-- GCC compatibility: Clang displays a warning on unsupported gcc
- optimization flags instead of an error.
+about them. The improvements since the 3.5 release include:
New Compiler Flags
-The integrated assembler is now turned on by default on ARM (and Thumb),
-so the use of the option `-fintegrated-as` is now redundant on those
-architectures. This is an important move to both *eat our own dog food*
-and to ease cross-compilation tremendously.
-We are aware of the problems that this may cause for code bases that
-rely on specific GNU syntax or extensions, and we're working towards
-getting them all fixed. Please, report bugs or feature requests if
-you find anything. In the meantime, use `-fno-integrated-as` to revert
-back the call to GNU assembler.
-In order to provide better diagnostics, the integrated assembler validates
-inline assembly when the integrated assembler is enabled. Because this is
-considered a feature of the compiler, it is controlled via the `fintegrated-as`
-and `fno-integrated-as` flags which enable and disable the integrated assembler
-respectively. `-integrated-as` and `-no-integrated-as` are now considered
-legacy flags (but are available as an alias to prevent breaking existing users),
-and users are encouraged to switch to the equivalent new feature flag.
-Deprecated flags `-faddress-sanitizer`, `-fthread-sanitizer`,
-`-fcatch-undefined-behavior` and `-fbounds-checking` were removed in favor of
-`-fsanitize=` family of flags.
-It is now possible to get optimization reports from the major transformation
-passes via three new flags: `-Rpass`, `-Rpass-missed` and `-Rpass-analysis`.
-These flags take a POSIX regular expression which indicates the name
-of the pass (or passes) that should emit optimization remarks.
+The option ....
-The option `-u` is forwarded to the linker on gnutools toolchains.
New Pragmas in Clang
-Loop optimization hints can be specified using the new `#pragma clang loop`
-directive just prior to the desired loop. The directive allows vectorization,
-interleaving, and unrolling to be enabled or disabled. Vector width as well
-as interleave and unrolling count can be manually specified. See language
-extensions for details.
-Clang now supports the `#pragma unroll` and `#pragma nounroll` directives to
-specify loop unrolling optimization hints. Placed just prior to the desired
-loop, `#pragma unroll` directs the loop unroller to attempt to fully unroll the
-loop. The pragma may also be specified with a positive integer parameter
-indicating the desired unroll count: `#pragma unroll _value_`. The unroll count
-parameter can be optionally enclosed in parentheses. The directive `#pragma
-nounroll` indicates that the loop should not be unrolled.
+Clang now supports the ...
-Clang's support for building native Windows programs, compatible with Visual
-C++, has improved significantly since the previous release. This includes
-correctly passing non-trivial objects by value, record layout, basic debug info,
-`Address Sanitizer <AddressSanitizer.html>`_ support, RTTI, name mangling,
-DLL attributes, and many many bug fixes. See
-`MSVC Compatibility <MSVCCompatibility.html>`_ for details.
-While still considered experimental, Clang's Windows support is good enough
-that Clang can self-host on Windows, and projects such as Chromium and Firefox
-have been built successfully using the
-`/fallback <UsersManual.html#the-fallback-option>`_ option.
+Clang's support for building native Windows programs ...
C Language Changes in Clang
@@ -168,7 +109,7 @@ OpenCL C Language Changes in Clang
Internal API Changes
-These are major API changes that have happened since the 3.4 release of
+These are major API changes that have happened since the 3.5 release of
Clang. If upgrading an external codebase that uses Clang as a library,
this section should help get you past the largest hurdles of upgrading.
@@ -182,16 +123,6 @@ libclang
-The `-analyzer-config` options are now passed from scan-build through to
-ccc-analyzer and then to Clang.
-With the option `-analyzer-config stable-report-filename=true`,
-instead of `report-XXXXXX.html`, scan-build/clang analyzer generate
-`report-<filename>-<function, method name>-<function position>-<id>.html`.
-(id = i++ for several issues found in the same function/method).
-List the function/method name in the index page of scan-build.
Core Analysis Improvements
More information about the cfe-commits