Skip to content

Latest commit

 

History

History
246 lines (165 loc) · 6.56 KB

ReleaseNotes.rst

File metadata and controls

246 lines (165 loc) · 6.56 KB

Clang 6.0.0 (In-Progress) Release Notes

Written by the LLVM Team

Warning

These are in-progress notes for the upcoming Clang 6 release. Release notes for previous releases can be found on the Download Page.

This document contains the release notes for the Clang C/C++/Objective-C frontend, part of the LLVM Compiler Infrastructure, release 6.0.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 the LLVM documentation. All LLVM releases may be downloaded from the LLVM releases web site.

For more information about Clang or LLVM, including information about the latest release, please see the Clang Web Site or the LLVM 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

  • -Wpragma-pack is a new warning that warns in the following cases:
    • When a translation unit is missing terminating #pragma pack (pop) directives.
    • When leaving an included file that changes the current alignment value, i.e. when the alignment before #include is different to the alignment after #include.
    • -Wpragma-pack-suspicious-include (disabled by default) warns on an #include when the included file contains structures or unions affected by a non-default alignment that has been specified using a #pragma pack directive prior to the #include.
  • -Wobjc-messaging-id is a new, non-default warning that warns about message sends to unqualified id in Objective-C. This warning is useful for projects that would like to avoid any potential future compiler errors/warnings, as the system frameworks might add a method with the same selector which could make the message send to id ambiguous.
  • Bitrig OS was merged back into OpenBSD, so Bitrig support has been removed from Clang/LLVM.
  • --autocomplete was implemented to obtain a list of flags and its arguments. This is used for shell autocompletion.

The following options are deprecated and ignored. They will be removed in future versions of Clang.

  • ...

Clang now supports the ...

  • The presence of __attribute__((availability(...))) on a declaration no longer implies default visibility for that declaration on macOS.
  • ...

Clang's support for building native Windows programs ...

  • ...

...

C11 Feature Support

...

...

C++1z Feature Support

...

...

...

...

These are major API changes that have happened since the 4.0.0 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.

  • ...

The hasDeclaration matcher now works the same for Type and QualType and only ever looks through one level of sugaring in a limited number of cases.

There are two main patterns affected by this:

  • qualType(hasDeclaration(recordDecl(...))): previously, we would look through sugar like TypedefType to get at the underlying recordDecl; now, we need to explicitly remove the sugaring: qualType(hasUnqualifiedDesugaredType(hasDeclaration(recordDecl(...))))
  • hasType(recordDecl(...)): hasType internally uses hasDeclaration; previously, this matcher used to match for example TypedefTypes of the RecordType, but after the change they don't; to fix, use:
::
hasType(hasUnqualifiedDesugaredType(
recordType(hasDeclaration(recordDecl(...)))))
  • templateSpecializationType(hasDeclaration(classTemplateDecl(...))): previously, we would directly match the underlying ClassTemplateDecl; now, we can explicitly match the ClassTemplateSpecializationDecl, but that requires to explicitly get the ClassTemplateDecl:
::
templateSpecializationType(hasDeclaration(
classTemplateSpecializationDecl(
hasSpecializedTemplate(classTemplateDecl(...)))))

...

  • Option -verbose added to the command line. Shows the list of processed files.

...

...

...

  • ...
  • ...

The following methods have been added:

  • ...

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.