Clang 3.9 (In-Progress) Release Notes¶
- What’s New in Clang 3.9?
- Core Analysis Improvements
- New Issues Found
- Significant Known Problems
- Additional Information
Written by the LLVM Team
These are in-progress notes for the upcoming Clang 3.9 release. You may prefer the Clang 3.8 Release Notes.
This document contains the release notes for the Clang C/C++/Objective-C frontend, part of the LLVM Compiler Infrastructure, release 3.9. 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 documentation. All LLVM releases may be downloaded from the LLVM releases web site.
Note that if you are reading this file from a Subversion checkout or the main Clang web page, this document applies to the next release, not the current one. To see the release notes for a specific release, please see the releases page.
Some of the major new features and improvements to Clang are listed here. Generic improvements to Clang as a whole or to its underlying infrastructure are described first, followed by language-specific sections with improvements to Clang’s support for those languages.
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.7 release include:
Clang’s support for building native Windows programs ...
TLS is enabled for Cygwin defaults to -femulated-tls.
The -faltivec and -maltivec flags no longer silently include altivec.h on Power platforms.
C11 Feature Support¶
These are major API changes that have happened since the 3.8 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.
- hasAnyArgument: Matcher no longer ignores parentheses and implicit casts on the argument before applying the inner matcher. The fix was done to allow for greater control by the user. In all existing checkers that use this matcher all instances of code hasAnyArgument(<inner matcher>) must be changed to hasAnyArgument(ignoringParenImpCasts(<inner matcher>)).
A wide variety of additional information is available on the Clang web page. 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 “clang/docs/” directory in the Clang tree.
If you have any questions or comments about Clang, please feel free to contact us via the mailing list.