2021-05-03 18:32:36 +02:00
|
|
|
========================================
|
2021-07-27 21:51:07 -07:00
|
|
|
Clang 14.0.0 (In-Progress) Release Notes
|
2020-02-13 22:46:33 +01:00
|
|
|
========================================
|
|
|
|
|
|
|
|
|
|
.. contents::
|
|
|
|
|
:local:
|
|
|
|
|
:depth: 2
|
|
|
|
|
|
|
|
|
|
Written by the `LLVM Team <https://llvm.org/>`_
|
|
|
|
|
|
|
|
|
|
.. warning::
|
|
|
|
|
|
2021-07-27 21:51:07 -07:00
|
|
|
These are in-progress notes for the upcoming Clang 14 release.
|
2020-02-13 22:46:33 +01:00
|
|
|
Release notes for previous releases can be found on
|
|
|
|
|
`the Download Page <https://releases.llvm.org/download.html>`_.
|
|
|
|
|
|
|
|
|
|
Introduction
|
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
This document contains the release notes for the Clang C/C++/Objective-C
|
2021-07-27 21:51:07 -07:00
|
|
|
frontend, part of the LLVM Compiler Infrastructure, release 14.0.0. Here we
|
2020-02-13 22:46:33 +01:00
|
|
|
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 <https://llvm.org/docs/ReleaseNotes.html>`_. All LLVM
|
|
|
|
|
releases may be downloaded from the `LLVM releases web
|
|
|
|
|
site <https://llvm.org/releases/>`_.
|
|
|
|
|
|
|
|
|
|
For more information about Clang or LLVM, including information about the
|
|
|
|
|
latest release, please see the `Clang Web Site <https://clang.llvm.org>`_ or the
|
|
|
|
|
`LLVM Web Site <https://llvm.org>`_.
|
|
|
|
|
|
|
|
|
|
Note that if you are reading this file from a Git 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 <https://llvm.org/releases/>`_.
|
|
|
|
|
|
2021-07-27 21:51:07 -07:00
|
|
|
What's New in Clang 14.0.0?
|
2020-02-13 22:46:33 +01:00
|
|
|
===========================
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
Major New Features
|
|
|
|
|
------------------
|
|
|
|
|
|
2021-07-27 21:51:07 -07:00
|
|
|
- ...
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
|
Improvements to Clang's diagnostics
|
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
2021-10-10 22:25:33 +02:00
|
|
|
- -Wbitwise-instead-of-logical (part of -Wbool-operation) warns about use of bitwise operators with boolean operands which have side effects.
|
2020-06-04 09:45:04 -07:00
|
|
|
|
2021-12-07 11:48:07 -05:00
|
|
|
- Added diagnostic groups to control diagnostics for attribute extensions by
|
|
|
|
|
adding groups ``-Wc++N-attribute-extensions`` (where ``N`` is the standard
|
|
|
|
|
release being diagnosed against). These new groups are automatically implied
|
|
|
|
|
when passing ``-Wc++N-extensions``. Resolves PR33518.
|
|
|
|
|
|
2022-01-20 19:36:16 +01:00
|
|
|
- Support ``-Wdeclaration-after-statement`` with C99 and later standards, and
|
|
|
|
|
not just C89, matching GCC's behaviour. A notable usecase is supporting style
|
|
|
|
|
guides that forbid mixing declarations and code, but want to move to newer C
|
|
|
|
|
standards.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Non-comprehensive list of changes in this release
|
|
|
|
|
-------------------------------------------------
|
|
|
|
|
|
2021-09-14 07:33:33 -07:00
|
|
|
- Maximum _ExtInt size was decreased from 16,777,215 bits to 8,388,608 bits.
|
|
|
|
|
Motivation for this was discussed in PR51829.
|
2021-12-30 13:42:13 -05:00
|
|
|
- Configuration file syntax extended with ``<CFGDIR>`` token. This expands to
|
|
|
|
|
the base path of the current config file. See :ref:`configuration-files` for
|
|
|
|
|
details.
|
2020-05-25 20:44:35 +02:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
New Compiler Flags
|
|
|
|
|
------------------
|
|
|
|
|
|
2021-11-04 17:40:51 +01:00
|
|
|
- Clang plugin arguments can now be passed through the compiler driver via
|
|
|
|
|
``-fplugin-arg-pluginname-arg``, similar to GCC's ``-fplugin-arg``.
|
2021-07-20 10:12:20 -04:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Deprecated Compiler Flags
|
|
|
|
|
-------------------------
|
|
|
|
|
|
2021-10-28 13:37:27 +02:00
|
|
|
- -Wweak-template-vtables has been deprecated and no longer has any effect. The
|
|
|
|
|
flag will be removed in the next release.
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
|
Modified Compiler Flags
|
|
|
|
|
-----------------------
|
|
|
|
|
|
2021-08-30 23:23:23 -07:00
|
|
|
- Support has been added for the following processors (``-mcpu`` identifiers in parentheses):
|
|
|
|
|
|
2021-09-03 14:16:29 -07:00
|
|
|
- RISC-V SiFive E20 (``sifive-e20``).
|
|
|
|
|
- RISC-V SiFive E21 (``sifive-e21``).
|
|
|
|
|
- RISC-V SiFive E24 (``sifive-e24``).
|
|
|
|
|
- RISC-V SiFive E34 (``sifive-e34``).
|
|
|
|
|
- RISC-V SiFive S21 (``sifive-s21``).
|
2021-08-30 23:23:23 -07:00
|
|
|
- RISC-V SiFive S51 (``sifive-s51``).
|
2021-09-03 14:16:29 -07:00
|
|
|
- RISC-V SiFive S54 (``sifive-s54``).
|
|
|
|
|
- RISC-V SiFive S76 (``sifive-s76``).
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2021-10-12 08:41:07 +01:00
|
|
|
- Support has been added for the following architectures (``-march`` identifiers in parentheses):
|
|
|
|
|
|
|
|
|
|
- Armv9-A (``armv9-a``).
|
|
|
|
|
- Armv9.1-A (``armv9.1-a``).
|
|
|
|
|
- Armv9.2-A (``armv9.2-a``).
|
|
|
|
|
|
2020-12-17 09:23:02 -05:00
|
|
|
Removed Compiler Flags
|
|
|
|
|
-------------------------
|
|
|
|
|
|
2021-07-27 21:51:07 -07:00
|
|
|
- ...
|
2021-02-24 17:01:51 +08:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
New Pragmas in Clang
|
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
|
|
- ...
|
|
|
|
|
|
|
|
|
|
Attribute Changes in Clang
|
|
|
|
|
--------------------------
|
|
|
|
|
|
2021-08-10 17:56:32 +02:00
|
|
|
- Attributes loaded as clang plugins which are sensitive to LangOpts must
|
|
|
|
|
now override ``acceptsLangOpts`` instead of ``diagLangOpts``.
|
|
|
|
|
Returning false will produce a generic "attribute ignored" diagnostic, as
|
|
|
|
|
with clang's built-in attributes.
|
|
|
|
|
If plugins want to provide richer diagnostics, they can do so when the
|
|
|
|
|
attribute is handled instead, e.g. in ``handleDeclAttribute``.
|
|
|
|
|
(This was changed in order to better support attributes in code completion).
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2021-10-17 07:54:48 -04:00
|
|
|
- __has_cpp_attribute, __has_c_attribute, __has_attribute, and __has_declspec
|
|
|
|
|
will now macro expand their argument. This causes a change in behavior for
|
|
|
|
|
code using ``__has_cpp_attribute(__clang__::attr)`` (and same for
|
|
|
|
|
``__has_c_attribute``) where it would previously expand to ``0`` for all
|
|
|
|
|
attributes, but will now issue an error due to the expansion of the
|
|
|
|
|
predefined ``__clang__`` macro.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Windows Support
|
|
|
|
|
---------------
|
|
|
|
|
|
2021-08-25 11:34:00 -07:00
|
|
|
- An MSVC compatibility workaround for C++ operator names was removed. As a
|
|
|
|
|
result, the ``<query.h>`` Windows SDK header may not compile out of the box.
|
|
|
|
|
Users should use a recent SDK and pass ``-DQUERY_H_RESTRICTION_PERMISSIVE``
|
|
|
|
|
or pass ``/permissive`` to disable C++ operator names altogether. See
|
|
|
|
|
`PR42427 <https://llvm.org/pr42427>` for more info.
|
|
|
|
|
|
[clang-cl] Support the /HOTPATCH flag
This patch adds support for the MSVC /HOTPATCH flag: https://docs.microsoft.com/sv-se/cpp/build/reference/hotpatch-create-hotpatchable-image?view=msvc-170&viewFallbackFrom=vs-2019
The flag is translated to a new -fms-hotpatch flag, which in turn adds a 'patchable-function' attribute for each function in the TU. This is then picked up by the PatchableFunction pass which would generate a TargetOpcode::PATCHABLE_OP of minsize = 2 (which means the target instruction must resolve to at least two bytes). TargetOpcode::PATCHABLE_OP is only implemented for x86/x64. When targetting ARM/ARM64, /HOTPATCH isn't required (instructions are always 2/4 bytes and suitable for hotpatching).
Additionally, when using /Z7, we generate a 'hot patchable' flag in the CodeView debug stream, in the S_COMPILE3 record. This flag is then picked up by LLD (or link.exe) and is used in conjunction with the linker /FUNCTIONPADMIN flag to generate extra space before each function, to accommodate for live patching long jumps. Please see: https://github.com/llvm/llvm-project/blob/d703b922961e0d02a5effdd4bfbb23ad50a3cc9f/lld/COFF/Writer.cpp#L1298
The outcome is that we can finally use Live++ or Recode along with clang-cl.
NOTE: It seems that MSVC cl.exe always enables /HOTPATCH on x64 by default, although if we did the same I thought we might generate sub-optimal code (if this flag was active by default). Additionally, MSVC always generates a .debug$S section and a S_COMPILE3 record, which Clang doesn't do without /Z7. Therefore, the following MSVC command-line "cl /c file.cpp" would have to be written with Clang such as "clang-cl /c file.cpp /HOTPATCH /Z7" in order to obtain the same result.
Depends on D43002, D80833 and D81301 for the full feature.
Differential Revision: https://reviews.llvm.org/D116511
2022-01-20 11:04:46 -05:00
|
|
|
- Add support for MSVC-compatible ``/hotpatch`` flag in clang-cl, and equivalent
|
|
|
|
|
-cc1 flag ``-fms-hotpatch``. Along with the linker flag ``/functionpadmin``
|
|
|
|
|
this creates executable images suitable for runtime code patching. This flag
|
|
|
|
|
is only required for x86/x64 targets; ARM/ARM64 simply needs the linker
|
|
|
|
|
``/functionpadmin``.
|
|
|
|
|
|
|
|
|
|
With this addition, clang-cl can be used in live code patching scenarios,
|
|
|
|
|
along with tools such as Live++ or Recode. Microsoft Edit and Continue isn't
|
|
|
|
|
currently supported.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
C Language Changes in Clang
|
|
|
|
|
---------------------------
|
|
|
|
|
|
2021-10-17 09:22:29 -04:00
|
|
|
- The value of ``__STDC_VERSION__`` has been bumped to ``202000L`` when passing
|
|
|
|
|
``-std=c2x`` so that it can be distinguished from C17 mode. This value is
|
|
|
|
|
expected to change again when C23 is published.
|
2021-08-20 11:10:53 -04:00
|
|
|
- Wide multi-characters literals such as ``L'ab'`` that would previously be interpreted as ``L'b'``
|
|
|
|
|
are now ill-formed in all language modes. The motivation for this change is outlined in
|
|
|
|
|
`P2362 <wg21.link/P2362>`_.
|
2021-08-25 10:18:13 -07:00
|
|
|
- Support for ``__attribute__((error("")))`` and
|
|
|
|
|
``__attribute__((warning("")))`` function attributes have been added.
|
2021-10-11 10:19:43 -07:00
|
|
|
- The maximum allowed alignment has been increased from 2^29 to 2^32.
|
2021-12-06 12:46:54 -05:00
|
|
|
- Clang now supports the ``_BitInt(N)`` family of bit-precise integer types
|
|
|
|
|
from C23. This type was previously exposed as ``_ExtInt(N)``, which is now a
|
|
|
|
|
deprecated alias for ``_BitInt(N)`` (so diagnostics will mention ``_BitInt``
|
|
|
|
|
even if source uses ``_ExtInt``). ``_BitInt(N)`` and ``_ExtInt(N)`` are the
|
|
|
|
|
same types in all respects beyond spelling and the deprecation warning.
|
|
|
|
|
``_BitInt(N)`` is supported as an extension in older C modes and in all C++
|
|
|
|
|
modes. Note: the ABI for ``_BitInt(N)`` is still in the process of being
|
|
|
|
|
stabilized, so this type should not yet be used in interfaces that require
|
|
|
|
|
ABI stability.
|
2022-01-11 11:51:22 -08:00
|
|
|
- When using ``asm goto`` with outputs whose constraint modifier is ``"+"``, we
|
|
|
|
|
now change the numbering of the labels to occur after hidden tied inputs for
|
|
|
|
|
better compatibility with GCC. For better portability between different
|
|
|
|
|
compilers and versions, symbolic references rather than numbered references
|
|
|
|
|
should be preferred. See
|
|
|
|
|
`this thread <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103640>` for more
|
|
|
|
|
info.
|
2021-12-06 12:46:54 -05:00
|
|
|
|
2022-01-13 11:45:27 -05:00
|
|
|
- Implemented `WG14 N2412 <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2412.pdf>`_,
|
|
|
|
|
which adds ``*_WIDTH`` macros to limits.h and stdint.h to report the bit
|
|
|
|
|
width of various integer datatypes.
|
|
|
|
|
|
2022-01-18 13:40:47 -05:00
|
|
|
- The ``ATOMIC_VAR_INIT`` macro from ``<stdatomic.h>`` is now diagnosed as
|
|
|
|
|
deprecated in C17 and later. The diagnostic can be disabled by defining the
|
|
|
|
|
``_CLANG_DISABLE_CRT_DEPRECATION_WARNINGS`` macro prior to including the
|
|
|
|
|
header.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
C++ Language Changes in Clang
|
|
|
|
|
-----------------------------
|
|
|
|
|
|
2020-07-15 11:40:53 +02:00
|
|
|
- ...
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2021-04-14 04:18:23 -07:00
|
|
|
C++20 Feature Support
|
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^
|
2022-01-18 13:40:47 -05:00
|
|
|
|
|
|
|
|
- The ``ATOMIC_VAR_INIT`` and ``ATOMIC_FLAG_INIT`` macros from the C standard
|
|
|
|
|
library ``<stdatomic.h>`` header are now diagnosed as deprecated in C++20 and
|
|
|
|
|
later. Note, the behavior is specific to the inclusion of ``<stdatomic.h>``
|
|
|
|
|
in C++ code; the STL ``<atomic>`` header also controls the behavior of these
|
|
|
|
|
macros and is not affected by these changes. The ``<stdatomic.h>`` diagnostic
|
|
|
|
|
can be disabled by defining the ``_CLANG_DISABLE_CRT_DEPRECATION_WARNINGS``
|
|
|
|
|
macro prior to including the header.
|
|
|
|
|
|
2021-04-14 04:18:23 -07:00
|
|
|
|
|
|
|
|
C++2b Feature Support
|
2020-02-13 22:46:33 +01:00
|
|
|
^^^^^^^^^^^^^^^^^^^^^
|
2021-10-05 16:38:01 -04:00
|
|
|
- Implemented `P1938R3: if consteval <https://wg21.link/P1938R3>`_.
|
2021-10-08 07:12:46 -04:00
|
|
|
- Implemented `P2360R0: Extend init-statement to allow alias-declaration <https://wg21.link/P2360R0>`_.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2021-08-17 14:39:58 -07:00
|
|
|
CUDA Language Changes in Clang
|
2021-08-23 13:45:13 -07:00
|
|
|
------------------------------
|
2021-08-17 14:39:58 -07:00
|
|
|
|
2021-11-05 09:13:33 +00:00
|
|
|
- Clang now supports CUDA versions up to 11.5.
|
2021-08-17 14:39:58 -07:00
|
|
|
- Default GPU architecture has been changed from sm_20 to sm_35.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Objective-C Language Changes in Clang
|
|
|
|
|
-------------------------------------
|
|
|
|
|
|
|
|
|
|
OpenCL C Language Changes in Clang
|
|
|
|
|
----------------------------------
|
|
|
|
|
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
ABI Changes in Clang
|
|
|
|
|
--------------------
|
|
|
|
|
|
2021-12-06 12:46:54 -05:00
|
|
|
- The ``_ExtInt(N)`` extension has been standardized in C23 as ``_BitInt(N)``.
|
2021-12-07 07:56:40 -05:00
|
|
|
The mangling of this type in C++ has accordingly changed: under the Microsoft
|
|
|
|
|
ABI it is now mangled using the ``_BitInt`` spelling, and under the Itanium ABI
|
|
|
|
|
it is now mangled using a dedicated production. Note: the ABI for ``_BitInt(N)``
|
|
|
|
|
is still in the process of being stabilized, so this type should not yet be
|
|
|
|
|
used in interfaces that require ABI stability.
|
2021-12-06 12:46:54 -05:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
OpenMP Support in Clang
|
|
|
|
|
-----------------------
|
|
|
|
|
|
2021-09-03 16:44:22 +05:30
|
|
|
- ``clang-nvlink-wrapper`` tool introduced to support linking of cubin files archived in an archive. See :doc:`ClangNvlinkWrapper`.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
|
CUDA Support in Clang
|
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
|
|
- ...
|
|
|
|
|
|
2020-08-20 21:37:51 +01:00
|
|
|
X86 Support in Clang
|
|
|
|
|
--------------------
|
|
|
|
|
|
2021-08-10 11:18:40 +08:00
|
|
|
- Support for ``AVX512-FP16`` instructions has been added.
|
2020-10-30 12:58:05 +08:00
|
|
|
|
2021-10-15 14:29:57 +01:00
|
|
|
Arm and AArch64 Support in Clang
|
|
|
|
|
--------------------------------
|
|
|
|
|
|
|
|
|
|
- Support has been added for the following processors (command-line identifiers in parentheses):
|
|
|
|
|
- Arm Cortex-A510 (``cortex-a510``)
|
2021-11-01 11:55:24 +00:00
|
|
|
- Arm Cortex-X2 (``cortex-x2``)
|
2021-10-14 15:21:42 +01:00
|
|
|
- Arm Cortex-A710 (``cortex-A710``)
|
2021-11-01 11:55:24 +00:00
|
|
|
|
2021-09-22 14:56:30 +01:00
|
|
|
- The -mtune flag is no longer ignored for AArch64. It is now possible to
|
2021-10-19 15:11:05 +01:00
|
|
|
tune code generation for a particular CPU with -mtune without setting any
|
|
|
|
|
architectural features. For example, compiling with
|
|
|
|
|
"-mcpu=generic -mtune=cortex-a57" will not enable any Cortex-A57 specific
|
|
|
|
|
architecture features, but will enable certain optimizations specific to
|
|
|
|
|
Cortex-A57 CPUs and enable the use of a more accurate scheduling model.
|
2021-09-22 14:56:30 +01:00
|
|
|
|
2021-11-09 09:35:25 -05:00
|
|
|
|
|
|
|
|
Floating Point Support in Clang
|
|
|
|
|
-------------------------------
|
2021-11-15 14:31:59 -05:00
|
|
|
- The default setting of FP contraction (FMA) is now -ffp-contract=on (for
|
|
|
|
|
languages other than CUDA/HIP) even when optimization is off. Previously,
|
|
|
|
|
the default behavior was equivalent to -ffp-contract=off (-ffp-contract
|
|
|
|
|
was not set).
|
|
|
|
|
Related to this, the switch -ffp-model=precise now implies -ffp-contract=on
|
|
|
|
|
rather than -ffp-contract=fast, and the documentation of these features has
|
|
|
|
|
been clarified. Previously, the documentation claimed that -ffp-model=precise
|
|
|
|
|
was the default, but this was incorrect because the precise model implied
|
2021-12-13 16:08:18 -08:00
|
|
|
-ffp-contract=fast, whereas the (now corrected) default behavior is
|
2021-11-15 14:31:59 -05:00
|
|
|
-ffp-contract=on.
|
2021-11-09 09:35:25 -05:00
|
|
|
-ffp-model=precise is now exactly the default mode of the compiler.
|
2022-01-08 11:10:05 -08:00
|
|
|
- -fstrict-float-cast-overflow no longer has target specific behavior. Clang
|
|
|
|
|
will saturate towards the smallest and largest representable integer values.
|
|
|
|
|
NaNs will be converted to zero.
|
2021-11-09 09:35:25 -05:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Internal API Changes
|
|
|
|
|
--------------------
|
|
|
|
|
|
2021-12-20 18:01:33 +01:00
|
|
|
- A new sugar ``Type`` AST node represents types accessed via a C++ using
|
|
|
|
|
declaration. Given code ``using std::error_code; error_code x;``, ``x`` has
|
|
|
|
|
a ``UsingType`` which desugars to the previous ``RecordType``.
|
Removed a RecursiveASTVisitor feature to visit operator kinds with different methods
Summary:
This feature was only used in two places, but contributed a non-trivial
amount to the complexity of RecursiveASTVisitor, and was buggy (see my
recent patches where I was fixing the bugs that I noticed). I don't
think the convenience benefit of this feature is worth the complexity.
Besides complexity, another issue with the current state of
RecursiveASTVisitor is the non-uniformity in how it handles different
AST nodes. All AST nodes follow a regular pattern, but operators are
special -- and this special behavior not documented. Correct usage of
RecursiveASTVisitor relies on shadowing member functions with specific
names and signatures. Near misses don't cause any compile-time errors,
incorrectly named or typed methods are just silently ignored. Therefore,
predictability of RecursiveASTVisitor API is quite important.
This change reduces the size of the `clang` binary by 38 KB (0.2%) in
release mode, and by 7 MB (0.3%) in debug mode. The `clang-tidy` binary
is reduced by 205 KB (0.3%) in release mode, and by 5 MB (0.4%) in debug
mode. I don't think these code size improvements are significant enough
to justify this change on its own (for me, the primary motivation is
reducing code complexity), but they I think are a nice side-effect.
Reviewers: rsmith, sammccall, ymandel, aaron.ballman
Reviewed By: rsmith, sammccall, ymandel, aaron.ballman
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D82921
2020-07-03 17:01:01 +02:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Build System Changes
|
|
|
|
|
--------------------
|
|
|
|
|
|
2021-12-14 10:08:59 -08:00
|
|
|
- Linux distros can specify ``-DCLANG_DEFAULT_PIE_ON_LINUX=On`` to use ``-fPIE`` and
|
|
|
|
|
``-pie`` by default. This matches GCC installations on many Linux distros
|
|
|
|
|
(configured with ``--enable-default-pie``).
|
|
|
|
|
(`D113372 <https://reviews.llvm.org/D113372>`_)
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
|
AST Matchers
|
|
|
|
|
------------
|
|
|
|
|
|
2021-10-11 19:56:10 +00:00
|
|
|
- ``TypeLoc`` AST Matchers are now available. These matchers provide helpful
|
|
|
|
|
utilities for matching ``TypeLoc`` nodes, such as the ``pointerTypeLoc``
|
|
|
|
|
matcher or the ``hasReturnTypeLoc`` matcher. The addition of these matchers
|
|
|
|
|
was made possible by changes to the handling of ``TypeLoc`` nodes that
|
|
|
|
|
allows them to enjoy the same static type checking as other AST node kinds.
|
2021-11-08 18:39:00 +00:00
|
|
|
- ``LambdaCapture`` AST Matchers are now available. These matchers allow for
|
|
|
|
|
the binding of ``LambdaCapture`` nodes. The ``LambdaCapture`` matchers added
|
|
|
|
|
include the ``lambdaCapture`` node matcher, the ``capturesVar`` traversal
|
|
|
|
|
matcher, and ``capturesThis`` narrowing matcher.
|
|
|
|
|
- The ``hasAnyCapture`` matcher now only accepts an inner matcher of type
|
|
|
|
|
``Matcher<LambdaCapture>``. The matcher originally accepted an inner matcher
|
|
|
|
|
of type ``Matcher<CXXThisExpr>`` or ``Matcher<VarDecl>``.
|
2021-12-20 18:01:33 +01:00
|
|
|
- The ``usingType`` matcher is now available and needed to refer to types that
|
|
|
|
|
are referred to via using C++ using declarations.
|
|
|
|
|
The associated ``UsingShadowDecl`` can be matched using ``throughUsingDecl``
|
|
|
|
|
and the underlying ``Type`` with ``hasUnderlyingType``.
|
|
|
|
|
``hasDeclaration`` continues to see through the alias and apply to the
|
|
|
|
|
underlying type.
|
2022-01-20 13:34:28 -05:00
|
|
|
- Added the ``isConsteval`` matcher to match ``consteval`` function
|
|
|
|
|
declarations as well as `if consteval` and `if ! consteval` statements.
|
2020-05-23 02:12:51 +01:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
clang-format
|
|
|
|
|
------------
|
|
|
|
|
|
2021-07-28 10:17:54 +02:00
|
|
|
- Option ``AllowShortEnumsOnASingleLine: false`` has been improved, it now
|
|
|
|
|
correctly places the opening brace according to ``BraceWrapping.AfterEnum``.
|
2021-06-26 15:20:17 +01:00
|
|
|
|
[clang-format] Add a BlockIndent option to AlignAfterOpenBracket
This style is similar to AlwaysBreak, but places closing brackets on new lines.
For example, if you have a multiline parameter list, clang-format currently only supports breaking per-parameter, but places the closing bracket on the line of the last parameter.
Function(
param1,
param2,
param3);
A style supported by other code styling tools (e.g. rustfmt) is to allow the closing brackets to be placed on their own line, aiding the user in being able to quickly infer the bounds of the block of code.
Function(
param1,
param2,
param3
);
For prior work on a similar feature, see: https://reviews.llvm.org/D33029.
Note: This currently only supports block indentation for closing parentheses.
Differential Revision: https://reviews.llvm.org/D109557
2022-01-17 08:54:51 +01:00
|
|
|
- Option ``AlignAfterOpenBracket: BlockIndent`` has been added. If set, it will
|
|
|
|
|
always break after an open bracket, if the parameters don't fit on a single
|
|
|
|
|
line. Closing brackets will be placed on a new line.
|
|
|
|
|
|
2021-12-13 16:08:18 -08:00
|
|
|
- Option ``QualifierAlignment`` has been added in order to auto-arrange the
|
2021-09-23 20:00:33 +01:00
|
|
|
positioning of specifiers/qualifiers
|
|
|
|
|
`const` `volatile` `static` `inline` `constexpr` `restrict`
|
|
|
|
|
in variable and parameter declarations to be either ``Right`` aligned
|
|
|
|
|
or ``Left`` aligned or ``Custom`` using ``QualifierOrder``.
|
|
|
|
|
|
|
|
|
|
- Option ``QualifierOrder`` has been added to allow the order
|
|
|
|
|
`const` `volatile` `static` `inline` `constexpr` `restrict`
|
|
|
|
|
to be controlled relative to the `type`.
|
|
|
|
|
|
2021-12-12 18:25:33 -08:00
|
|
|
- Option ``RemoveBracesLLVM`` has been added to remove optional braces of
|
|
|
|
|
control statements for the LLVM style.
|
|
|
|
|
|
2021-12-28 10:01:26 -05:00
|
|
|
- Option ``SeparateDefinitionBlocks`` has been added to insert or remove empty
|
|
|
|
|
lines between definition blocks including functions, classes, structs, enums,
|
|
|
|
|
and namespaces.
|
|
|
|
|
|
2021-11-07 20:56:35 +01:00
|
|
|
- Add a ``Custom`` style to ``SpaceBeforeParens``, to better configure the
|
|
|
|
|
space before parentheses. The custom options can be set using
|
|
|
|
|
``SpaceBeforeParensOptions``.
|
|
|
|
|
|
2022-01-03 11:37:20 +01:00
|
|
|
- The command line argument `-style=<string>` has been extended so that a specific
|
|
|
|
|
format file at location <format_file_path> can be selected. This is supported
|
|
|
|
|
via the syntax: `-style=file:<format_file_path>`.
|
|
|
|
|
|
2021-12-02 08:05:30 +00:00
|
|
|
- Improved C++20 Modules and Coroutines support.
|
2021-11-25 11:50:34 +00:00
|
|
|
|
2022-01-04 17:19:24 +01:00
|
|
|
- Option ``AfterOverloadedOperator`` has been added in ``SpaceBeforeParensOptions``
|
|
|
|
|
to allow space between overloaded operator and opening parentheses.
|
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
libclang
|
|
|
|
|
--------
|
|
|
|
|
|
|
|
|
|
- ...
|
|
|
|
|
|
|
|
|
|
Static Analyzer
|
|
|
|
|
---------------
|
|
|
|
|
|
|
|
|
|
- ...
|
|
|
|
|
|
|
|
|
|
.. _release-notes-ubsan:
|
|
|
|
|
|
|
|
|
|
Undefined Behavior Sanitizer (UBSan)
|
|
|
|
|
------------------------------------
|
|
|
|
|
|
|
|
|
|
Core Analysis Improvements
|
|
|
|
|
==========================
|
|
|
|
|
|
|
|
|
|
- ...
|
|
|
|
|
|
|
|
|
|
New Issues Found
|
|
|
|
|
================
|
|
|
|
|
|
|
|
|
|
- ...
|
|
|
|
|
|
|
|
|
|
Python Binding Changes
|
|
|
|
|
----------------------
|
|
|
|
|
|
|
|
|
|
The following methods have been added:
|
|
|
|
|
|
|
|
|
|
- ...
|
|
|
|
|
|
|
|
|
|
Significant Known Problems
|
|
|
|
|
==========================
|
|
|
|
|
|
|
|
|
|
Additional Information
|
|
|
|
|
======================
|
|
|
|
|
|
|
|
|
|
A wide variety of additional information is available on the `Clang web
|
|
|
|
|
page <https://clang.llvm.org/>`_. The web page contains versions of the
|
2020-03-22 22:18:40 +01:00
|
|
|
API documentation which are up-to-date with the Git version of
|
2020-02-13 22:46:33 +01:00
|
|
|
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 <https://lists.llvm.org/mailman/listinfo/cfe-dev>`_.
|