2022-02-01 23:13:01 -08:00
|
|
|
===========================================
|
|
|
|
Clang |release| |ReleaseNotesTitle|
|
|
|
|
===========================================
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
.. contents::
|
|
|
|
:local:
|
|
|
|
:depth: 2
|
|
|
|
|
|
|
|
Written by the `LLVM Team <https://llvm.org/>`_
|
|
|
|
|
2022-02-01 23:13:01 -08:00
|
|
|
.. only:: PreRelease
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2022-02-01 23:13:01 -08:00
|
|
|
.. warning::
|
|
|
|
These are in-progress notes for the upcoming Clang |version| release.
|
|
|
|
Release notes for previous releases can be found on
|
2023-02-15 23:53:38 +02:00
|
|
|
`the Releases Page <https://llvm.org/releases>`_.
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
Introduction
|
|
|
|
============
|
|
|
|
|
|
|
|
This document contains the release notes for the Clang C/C++/Objective-C
|
2022-02-01 23:13:01 -08:00
|
|
|
frontend, part of the LLVM Compiler Infrastructure, release |release|. 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
|
2023-02-15 23:53:38 +02:00
|
|
|
documentation <https://llvm.org/docs/ReleaseNotes.html>`_. For the libc++ release notes,
|
|
|
|
see `this page <https://libcxx.llvm.org/ReleaseNotes.html>`_. All LLVM releases
|
|
|
|
may be downloaded from the `LLVM releases web site <https://llvm.org/releases/>`_.
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
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>`_.
|
|
|
|
|
2022-09-15 07:29:49 -04:00
|
|
|
Potentially Breaking Changes
|
|
|
|
============================
|
|
|
|
These changes are ones which we think may surprise users when upgrading to
|
|
|
|
Clang |release| because of the opportunity they pose for disruption to existing
|
|
|
|
code bases.
|
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
|
|
|
|
C/C++ Language Potentially Breaking Changes
|
|
|
|
-------------------------------------------
|
2023-02-16 17:49:39 -08:00
|
|
|
- Indirect edges of asm goto statements under certain circumstances may now be
|
|
|
|
split. In previous releases of clang, that means for the following code the
|
|
|
|
two inputs may have compared equal in the inline assembly. This is no longer
|
|
|
|
guaranteed (and necessary to support outputs along indirect edges, which is
|
|
|
|
now supported as of this release). This change is more consistent with the
|
|
|
|
behavior of GCC.
|
|
|
|
|
|
|
|
.. code-block:: c
|
|
|
|
|
|
|
|
foo: asm goto ("# %0 %1"::"i"(&&foo)::foo);
|
2023-02-15 23:53:38 +02:00
|
|
|
|
|
|
|
C++ Specific Potentially Breaking Changes
|
|
|
|
-----------------------------------------
|
|
|
|
|
|
|
|
ABI Changes in This Version
|
|
|
|
---------------------------
|
|
|
|
|
2022-02-01 23:13:01 -08:00
|
|
|
What's New in Clang |release|?
|
|
|
|
==============================
|
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.
|
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
C++ Language Changes
|
|
|
|
--------------------
|
|
|
|
- Improved ``-O0`` code generation for calls to ``std::forward_like``. Similarly to
|
|
|
|
``std::move, std::forward`` et al. it is now treated as a compiler builtin and implemented
|
|
|
|
directly rather than instantiating the definition from the standard library.
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
C++20 Feature Support
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^
|
2022-03-12 20:49:01 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
C++2b Feature Support
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
Resolutions to C++ Defect Reports
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
C Language Changes
|
|
|
|
------------------
|
2023-02-16 17:49:39 -08:00
|
|
|
- Support for outputs from asm goto statements along indirect edges has been
|
|
|
|
added. This fixes
|
|
|
|
`Issue 53562 <https://github.com/llvm/llvm-project/issues/53562`_.
|
2023-02-15 23:53:38 +02:00
|
|
|
|
|
|
|
C2x Feature Support
|
|
|
|
^^^^^^^^^^^^^^^^^^^
|
|
|
|
- Implemented the ``unreachable`` macro in freestanding ``<stddef.h>`` for
|
|
|
|
`WG14 N2826 <https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2826.pdf>`_
|
2022-08-26 09:17:14 -04:00
|
|
|
|
2022-08-26 10:04:06 -04:00
|
|
|
Non-comprehensive list of changes in this release
|
|
|
|
-------------------------------------------------
|
2023-01-06 15:52:22 -03:00
|
|
|
- Clang now saves the address of ABI-indirect function parameters on the stack,
|
|
|
|
improving the debug information available in programs compiled without
|
|
|
|
optimizations.
|
2023-02-02 17:42:31 +00:00
|
|
|
- Clang now supports ``__builtin_nondeterministic_value`` that returns a
|
|
|
|
nondeterministic value of the same type as the provided argument.
|
2022-08-26 09:17:14 -04:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
New Compiler Flags
|
|
|
|
------------------
|
|
|
|
|
|
|
|
Deprecated Compiler Flags
|
|
|
|
-------------------------
|
|
|
|
|
|
|
|
Modified Compiler Flags
|
|
|
|
-----------------------
|
2023-01-23 13:25:55 +02:00
|
|
|
|
2020-12-17 09:23:02 -05:00
|
|
|
Removed Compiler Flags
|
|
|
|
-------------------------
|
2023-02-15 18:30:49 +08:00
|
|
|
- The deprecated flag `-fmodules-ts` is removed. Please use ``-std=c++20``
|
|
|
|
or higher to use standard C++ modules instead.
|
2020-12-17 09:23:02 -05:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Attribute Changes in Clang
|
|
|
|
--------------------------
|
2023-02-15 23:53:38 +02:00
|
|
|
- Introduced a new function attribute ``__attribute__((unsafe_buffer_usage))``
|
|
|
|
to be worn by functions containing buffer operations that could cause out of
|
|
|
|
bounds memory accesses. It emits warnings at call sites to such functions when
|
|
|
|
the flag ``-Wunsafe-buffer-usage`` is enabled.
|
|
|
|
- ``__declspec`` attributes can now be used together with the using keyword. Before
|
|
|
|
the attributes on ``__declspec`` was ignored, while now it will be forwarded to the
|
|
|
|
point where the alias is used.
|
2023-01-20 23:31:53 +00:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Improvements to Clang's diagnostics
|
|
|
|
-----------------------------------
|
|
|
|
- We now generate a diagnostic for signed integer overflow due to unary minus
|
|
|
|
in a non-constant expression context.
|
|
|
|
(`#31643 <https://github.com/llvm/llvm-project/issues/31643>`)
|
|
|
|
- Clang now warns by default for C++20 and later about deprecated capture of
|
|
|
|
``this`` with a capture default of ``=``. This warning can be disabled with
|
|
|
|
``-Wno-deprecated-this-capture``.
|
2023-01-31 11:43:34 -08:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Bug Fixes in This Version
|
|
|
|
-------------------------
|
2023-02-09 10:53:39 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
- Fix crash when diagnosing incorrect usage of ``_Nullable`` involving alias
|
|
|
|
templates.
|
|
|
|
(`#60344 <https://github.com/llvm/llvm-project/issues/60344>`_)
|
|
|
|
- Fix confusing warning message when ``/clang:-x`` is passed in ``clang-cl``
|
|
|
|
driver mode and emit an error which suggests using ``/TC`` or ``/TP``
|
|
|
|
``clang-cl`` options instead.
|
|
|
|
(`#59307 <https://github.com/llvm/llvm-project/issues/59307>`_)
|
2023-01-23 13:25:55 +02:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Bug Fixes to Compiler Builtins
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
2022-05-02 17:06:04 -04:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Bug Fixes to Attribute Support
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
2022-08-26 19:26:32 +08:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Bug Fixes to C++ Support
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^
|
2023-01-18 08:49:45 -05:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
- Fix crash on invalid code when looking up a destructor in a templated class
|
|
|
|
inside a namespace.
|
|
|
|
(`#59446 <https://github.com/llvm/llvm-project/issues/59446>`_)
|
|
|
|
- Fix crash when evaluating consteval constructor of derived class whose base
|
|
|
|
has more than one field.
|
|
|
|
(`#60166 <https://github.com/llvm/llvm-project/issues/60166>`_)
|
2022-08-11 12:53:41 -07:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Bug Fixes to AST Handling
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^
|
2023-01-17 11:29:04 -08:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Miscellaneous Bug Fixes
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Miscellaneous Clang Crashes Fixed
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
2022-05-03 14:13:56 -04:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Target Specific Changes
|
|
|
|
-----------------------
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
X86 Support
|
|
|
|
^^^^^^^^^^^
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Arm and AArch64 Support
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
- The hard-float ABI is now available in Armv8.1-M configurations that
|
|
|
|
have integer MVE instructions (and therefore have FP registers) but
|
|
|
|
no scalar or vector floating point computation. Previously, trying
|
|
|
|
to select the hard-float ABI on such a target (via
|
|
|
|
``-mfloat-abi=hard`` or a triple ending in ``hf``) would silently
|
|
|
|
use the soft-float ABI instead.
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
- Clang builtin ``__arithmetic_fence`` and the command line option ``-fprotect-parens``
|
|
|
|
are now enabled for AArch64.
|
2022-02-02 13:06:55 -05:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
Windows Support
|
|
|
|
^^^^^^^^^^^^^^^
|
2020-02-13 22:46:33 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
LoongArch Support
|
|
|
|
^^^^^^^^^^^^^^^^^
|
2023-01-17 20:53:58 +08:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
RISC-V Support
|
|
|
|
^^^^^^^^^^^^^^
|
2023-02-02 10:18:17 -08:00
|
|
|
- Added ``-mrvv-vector-bits=`` option to give an upper and lower bound on vector
|
|
|
|
length. Valid values are powers of 2 between 64 and 65536. A value of 32
|
|
|
|
should eventually be supported. We also accept "zvl" to use the Zvl*b
|
|
|
|
extension from ``-march`` or ``-mcpu`` to the be the upper and lower bound.
|
2022-08-18 14:39:37 -07:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
CUDA/HIP Language Changes
|
|
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^
|
2022-10-18 10:50:37 -07:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
CUDA Support
|
|
|
|
^^^^^^^^^^^^
|
2022-01-23 20:45:25 -08:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
AIX Support
|
|
|
|
^^^^^^^^^^^
|
[Clang][AArch64] Support AArch64 target(..) attribute formats.
This adds support under AArch64 for the target("..") attributes. The
current parsing is very X86-shaped, this patch attempts to bring it line
with the GCC implementation from
https://gcc.gnu.org/onlinedocs/gcc/AArch64-Function-Attributes.html#AArch64-Function-Attributes.
The supported formats are:
- "arch=<arch>" strings, that specify the architecture features for a
function as per the -march=arch+feature option.
- "cpu=<cpu>" strings, that specify the target-cpu and any implied
atributes as per the -mcpu=cpu+feature option.
- "tune=<cpu>" strings, that specify the tune-cpu cpu for a function as
per -mtune.
- "+<feature>", "+no<feature>" enables/disables the specific feature, for
compatibility with GCC target attributes.
- "<feature>", "no-<feature>" enabled/disables the specific feature, for
backward compatibility with previous releases.
To do this, the parsing of target attributes has been moved into
TargetInfo to give the target the opportunity to override the existing
parsing. The only non-aarch64 change should be a minor alteration to the
error message, specifying using "CPU" to describe the cpu, not
"architecture", and the DuplicateArch/Tune from ParsedTargetAttr have
been combined into a single option.
Differential Revision: https://reviews.llvm.org/D133848
2022-10-01 15:40:59 +01:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
WebAssembly Support
|
|
|
|
^^^^^^^^^^^^^^^^^^^
|
[ARM] Allow selecting hard-float ABI in integer-only MVE.
Armv8.1-M can be configured to support the integer subset of the MVE
vector instructions, and no floating point. In that situation, the FP
and vector registers still exist, and so do the load, store and move
instructions that transfer data in and out of them. So there's no
reason the hard floating point ABI can't be supported, and you might
reasonably want to use it, for the sake of intrinsics-based code
passing explicit MVE vector types between functions.
But the selection of the hard float ABI in the backend was gated on
Subtarget->hasVFP2Base(), which is false in the case of integer MVE
and no FP.
As a result, you'd silently get the soft float ABI even if you
deliberately tried to select it, e.g. with clang options such as
--target=arm-none-eabi -mfloat-abi=hard -march=armv8.1m.main+nofp+mve
The hard float ABI should have been gated on the weaker condition
Subtarget->hasFPRegs(), because the only requirement for being able to
pass arguments in the FP registers is that the registers themselves
should exist.
I haven't added a new test, because changing the existing
CodeGen/Thumb2/float-ops.ll test seemed sufficient. But I've added a
comment explaining why the results are expected to be what they are.
Reviewed By: lenary
Differential Revision: https://reviews.llvm.org/D142703
2023-01-31 17:31:33 +00:00
|
|
|
|
2023-02-15 23:53:38 +02:00
|
|
|
DWARF Support in Clang
|
|
|
|
----------------------
|
2023-02-13 18:29:16 +00:00
|
|
|
|
2021-11-09 09:35:25 -05:00
|
|
|
Floating Point Support in Clang
|
|
|
|
-------------------------------
|
2023-02-02 12:31:53 -08:00
|
|
|
- Add ``__builtin_elementwise_log`` builtin for floating point types only.
|
2023-02-07 11:26:08 -08:00
|
|
|
- Add ``__builtin_elementwise_log10`` builtin for floating point types only.
|
|
|
|
- Add ``__builtin_elementwise_log2`` builtin for floating point types only.
|
2021-11-09 09:35:25 -05:00
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
AST Matchers
|
|
|
|
------------
|
|
|
|
|
|
|
|
clang-format
|
|
|
|
------------
|
|
|
|
|
2023-02-06 18:47:11 +08:00
|
|
|
- Add ``NextLineOnly`` style to option ``PackConstructorInitializers``.
|
|
|
|
Compared to ``NextLine`` style, ``NextLineOnly`` style will not try to
|
|
|
|
put the initializers on the current line first, instead, it will try to
|
|
|
|
put the initializers on the next line only.
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
libclang
|
|
|
|
--------
|
2022-08-25 08:35:46 +02:00
|
|
|
|
2023-02-09 09:53:10 -05:00
|
|
|
- Introduced the new function ``clang_CXXMethod_isExplicit``,
|
|
|
|
which identifies whether a constructor or conversion function cursor
|
|
|
|
was marked with the explicit identifier.
|
|
|
|
|
2020-02-13 22:46:33 +01:00
|
|
|
Static Analyzer
|
|
|
|
---------------
|
[analyzer] Consider single-elem arrays as FAMs by default
According to my measurement in https://reviews.llvm.org/D108230#3933232,
it seems like there is no drawback to enabling this analyzer-config by default.
Actually, enabling this by default would make it consistent with the
codegen of clang, which according to `-fstrict-flex-arrays`, assumes
by default that all trailing arrays could be FAMs, let them be of size
undefined, zero, one, or anything else.
Speaking of `-fstrict-flex-arrays`, in the next patch I'll deprecate
the analyzer-config FAM option in favor of that flag. That way, CSA will
always be in sync with what the codegen will think of FAMs.
So, if a new codebase sets `-fstrict-flex-arrays` to some value above 0,
CSA will also make sure that only arrays of the right size will be
considered as FAMs.
Reviewed By: xazax.hun
Differential Revision: https://reviews.llvm.org/D138657
2022-11-25 10:24:56 +01:00
|
|
|
|
2022-09-26 17:41:37 -07:00
|
|
|
.. _release-notes-sanitizers:
|
|
|
|
|
|
|
|
Sanitizers
|
|
|
|
----------
|
2020-02-13 22:46:33 +01:00
|
|
|
|
|
|
|
|
|
|
|
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
|
2023-02-15 23:53:38 +02:00
|
|
|
contact us on the `Discourse forums (Clang Frontend category)
|
2022-07-01 14:07:48 -07:00
|
|
|
<https://discourse.llvm.org/c/clang/6>`_.
|