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-03-05 00:56:15 +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
-----------------------------------------
2023-02-20 10:26:41 +08:00
- Clang won't search for coroutine_traits in std::experimental namespace any more.
Clang will only search for std::coroutine_traits for coroutines then.
2023-02-15 23:53:38 +02:00
ABI Changes in This Version
---------------------------
2023-02-22 23:20:18 +02:00
- `` __is_trivial `` has changed for a small category of classes with constrained default constructors (`#60697 <https://github.com/llvm/llvm-project/issues/60697> `_ ).
*FIXME: Remove this note if we've backported this change to the Clang 16 branch.*
2023-02-15 23:53:38 +02:00
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.
2023-02-17 19:45:30 +01:00
- Implemented `CWG2518 <https://wg21.link/CWG2518> `_ which allows `` static_assert(false) ``
to not be ill-formed when its condition is evaluated in the context of a template definition.
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
^^^^^^^^^^^^^^^^^^^^^
2022-02-06 22:58:43 +01:00
- Implemented `P2036R3: Change scope of lambda trailing-return-type <https://wg21.link/P2036R3> `_
and `P2579R0 Mitigation strategies for P2036 <https://wg21.link/P2579R0> `_ .
These proposals modify how variables captured in lambdas can appear in trailing return type
expressions and how their types are deduced therein, in all C++ language versions.
2023-02-15 23:53:38 +02:00
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
2023-02-17 07:56:52 -05:00
`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
2023-02-24 13:52:41 -05:00
- Removed the `` ATOMIC_VAR_INIT `` macro in C2x and later standards modes, which
implements `WG14 N2886 <https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2886.htm> `_
[C2x] Implement support for revised spelling of keywords
This implements WG14 N2934
(https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2934.pdf), which
adds keywords for alignas, alignof, bool, static_assert, and
thread_local in C, as aliases for _Alignas, _Alignof, _Bool,
_Static_assert, and _Thread_local. We already supported the keywords in
C2x mode, but this completes support by adding pre-C2x compat warnings
and updates the stdalign.h header in freestanding mode.
2023-02-25 09:27:46 -05:00
- Implemented `WG14 N2934 <https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2934.pdf> `_
which introduces the `` bool `` , `` static_assert `` , `` alignas `` , `` alignof `` ,
and `` thread_local `` keywords in C2x.
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.
2023-02-23 14:31:41 +08:00
- The deprecated flag `-fcoroutines-ts` is removed. Please use `` -std=c++20 ``
or higher to use standard C++ coroutines 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-02-23 14:14:14 -08:00
- Introduced a new `` USR `` (unified symbol resolution) clause inside of the
2023-02-23 15:52:21 -08:00
existing `` __attribute__((external_source_symbol)) `` attribute. Clang's indexer
uses the optional USR value when indexing Clang's AST. This value is expected
to be generated by an external compiler when generating C++ bindings during
the compilation of the foreign language sources (e.g. Swift).
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-03-01 23:29:45 +01:00
- Clang had failed to emit some `` -Wundefined-internal `` for members of a local
class if that class was first introduced with a forward declaration.
2023-03-06 08:16:16 -08:00
- Diagnostic notes and fix-its are now generated for `` ifunc `` /`` alias `` attributes
which point to functions whose names are mangled.
2023-03-01 14:53:23 +00:00
- Diagnostics relating to macros on the command line of a preprocessed assembly
file are now reported as coming from the file `` <command line> `` instead of
`` <built-in> `` .
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-02-13 21:06:07 -08:00
- Fix assert that fails when the expression causing the this pointer to be
captured by a block is part of a constexpr if statement's branch and
instantiation of the enclosing method causes the branch to be discarded.
2023-02-17 14:56:02 -08:00
- Fix __VA_OPT__ implementation so that it treats the concatenation of a
non-placemaker token and placemaker token as a non-placemaker token.
(`#60268 <https://github.com/llvm/llvm-project/issues/60268> `_ )
2023-02-23 11:04:23 +01:00
- Fix crash when taking the address of a consteval lambda call operator.
(`#57682 <https://github.com/llvm/llvm-project/issues/57682> `_ )
2023-03-03 10:31:48 +08:00
- Clang now support export declarations in the language linkage.
(`#60405 <https://github.com/llvm/llvm-project/issues/60405> `_ )
2023-03-06 03:25:57 -05:00
- Fix aggregate initialization inside lambda constexpr.
(`#60936 <https://github.com/llvm/llvm-project/issues/60936> `_ )
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
2022-02-06 08:20:54 -05:00
AVR Support
^^^^^^^^^^^
- The definition of `` USHRT_MAX `` in the freestanding `` <limits.h> `` no longer
overflows on AVR (where `` sizeof(int) == sizeof(unsigned short) `` ). The type
of `` USHRT_MAX `` is now `` unsigned int `` instead of `` int `` , as required by
the C standard.
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
------------
2023-03-01 11:51:46 -05:00
- Add `` coroutineBodyStmt `` matcher.
- The `` hasBody `` matcher now matches coroutine body nodes in
`` CoroutineBodyStmts `` .
2020-02-13 22:46:33 +01:00
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.
[libclang] Add API to override preamble storage path
TempPCHFile::create() calls llvm::sys::fs::createTemporaryFile() to
create a file named preamble-*.pch in a system temporary directory. This
commit allows overriding the directory where these often many and large
preamble-*.pch files are stored.
The referenced bug report requests the ability to override the temporary
directory path used by libclang. However, overriding the return value of
llvm::sys::path::system_temp_directory() was rejected during code review
as improper and because it would negatively affect multithreading
performance. Finding all places where libclang uses the temporary
directory is very difficult. Therefore this commit is limited to
override libclang's single known use of the temporary directory.
This commit allows to override the preamble storage path only during
CXIndex construction to avoid multithreading issues and ensure that all
preambles are stored in the same directory. For the same multithreading
and consistency reasons, this commit deprecates
clang_CXIndex_setGlobalOptions() and
clang_CXIndex_setInvocationEmissionPathOption() in favor of specifying
these options during CXIndex construction.
Adding a new CXIndex constructor function each time a new initialization
argument is needed leads to either a large number of function parameters
unneeded by most libclang users or to an exponential number of overloads
that support different usage requirements. Therefore this commit
introduces a new extensible struct CXIndexOptions and a general function
clang_createIndexWithOptions().
A libclang user passes a desired preamble storage path to
clang_createIndexWithOptions(), which stores it in
CIndexer::PreambleStoragePath. Whenever
clang_parseTranslationUnit_Impl() is called, it passes
CIndexer::PreambleStoragePath to ASTUnit::LoadFromCommandLine(), which
stores this argument in ASTUnit::PreambleStoragePath. Whenever
ASTUnit::getMainBufferWithPrecompiledPreamble() is called, it passes
ASTUnit::PreambleStoragePath to PrecompiledPreamble::Build().
PrecompiledPreamble::Build() forwards the corresponding StoragePath
argument to TempPCHFile::create(). If StoragePath is not empty,
TempPCHFile::create() stores the preamble-*.pch file in the directory at
the specified path rather than in the system temporary directory.
The analysis below proves that this passing around of the
PreambleStoragePath string is sufficient to guarantee that the libclang
user override is used in TempPCHFile::create(). The analysis ignores API
uses in test code.
TempPCHFile::create() is called only in PrecompiledPreamble::Build().
PrecompiledPreamble::Build() is called only in two places: one in
clangd, which is not used by libclang, and one in
ASTUnit::getMainBufferWithPrecompiledPreamble().
ASTUnit::getMainBufferWithPrecompiledPreamble() is called in 3 places:
ASTUnit::LoadFromCompilerInvocation() [analyzed below].
ASTUnit::Reparse(), which in turn is called only from
clang_reparseTranslationUnit_Impl(), which in turn is called only from
clang_reparseTranslationUnit(). clang_reparseTranslationUnit() is never
called in LLVM code, but is part of public libclang API. This function's
documentation requires its translation unit argument to have been built
with clang_createTranslationUnitFromSourceFile().
clang_createTranslationUnitFromSourceFile() delegates its work to
clang_parseTranslationUnit(), which delegates to
clang_parseTranslationUnit2(), which delegates to
clang_parseTranslationUnit2FullArgv(), which delegates to
clang_parseTranslationUnit_Impl(), which passes
CIndexer::PreambleStoragePath to the ASTUnit it creates.
ASTUnit::CodeComplete() passes AllowRebuild = false to
ASTUnit::getMainBufferWithPrecompiledPreamble(), which makes it return
nullptr before calling PrecompiledPreamble::Build().
Both ASTUnit::LoadFromCompilerInvocation() overloads (one of which
delegates its work to another) call
ASTUnit::getMainBufferWithPrecompiledPreamble() only if their argument
PrecompilePreambleAfterNParses > 0. LoadFromCompilerInvocation() is
called in:
ASTBuilderAction::runInvocation() keeps the default parameter value
of PrecompilePreambleAfterNParses = 0, meaning that the preamble file is
never created from here.
ASTUnit::LoadFromCommandLine().
ASTUnit::LoadFromCommandLine() is called in two places:
CrossTranslationUnitContext::ASTLoader::loadFromSource() keeps the
default parameter value of PrecompilePreambleAfterNParses = 0, meaning
that the preamble file is never created from here.
clang_parseTranslationUnit_Impl(), which passes
CIndexer::PreambleStoragePath to the ASTUnit it creates.
Therefore, the overridden preamble storage path is always used in
TempPCHFile::create().
TempPCHFile::create() uses PreambleStoragePath in the same way as
LibclangInvocationReporter() uses InvocationEmissionPath. The existing
documentation for clang_CXIndex_setInvocationEmissionPathOption() does
not specify ownership, encoding, separator or relative vs absolute path
requirements. So the documentation for
CXIndexOptions::PreambleStoragePath doesn't either. The assumptions are:
no ownership transfer;
UTF-8 encoding;
native separators.
Both relative and absolute paths are supported.
The added API works as expected in KDevelop:
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/283
Fixes: https://github.com/llvm/llvm-project/issues/51847
Differential Revision: https://reviews.llvm.org/D143418
2023-03-07 08:24:23 -05:00
- Introduced the new `` CXIndex `` constructor function
`` clang_createIndexWithOptions `` , which allows overriding precompiled preamble
storage path.
- Deprecated two functions `` clang_CXIndex_setGlobalOptions `` and
`` clang_CXIndex_setInvocationEmissionPathOption `` in favor of the new
function `` clang_createIndexWithOptions `` in order to improve thread safety.
2020-02-13 22:46:33 +01:00
Static Analyzer
---------------
2023-02-28 16:42:32 -08:00
- Fix incorrect alignment attribute on the this parameter of certain
non-complete destructors when using the Microsoft ABI.
`Issue 60465 <https://github.com/llvm/llvm-project/issues/60465> `_ .
[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> `_.