1===========================================
2Clang |release| |ReleaseNotesTitle|
3===========================================
4
5.. contents::
6   :local:
7   :depth: 2
8
9Written by the `LLVM Team <https://llvm.org/>`_
10
11.. only:: PreRelease
12
13  .. warning::
14     These are in-progress notes for the upcoming Clang |version| release.
15     Release notes for previous releases can be found on
16     `the Download Page <https://releases.llvm.org/download.html>`_.
17
18Introduction
19============
20
21This document contains the release notes for the Clang C/C++/Objective-C
22frontend, part of the LLVM Compiler Infrastructure, release |release|. Here we
23describe the status of Clang in some detail, including major
24improvements from the previous release and new feature work. For the
25general LLVM release notes, see `the LLVM
26documentation <https://llvm.org/docs/ReleaseNotes.html>`_. All LLVM
27releases may be downloaded from the `LLVM releases web
28site <https://llvm.org/releases/>`_.
29
30For more information about Clang or LLVM, including information about the
31latest release, please see the `Clang Web Site <https://clang.llvm.org>`_ or the
32`LLVM Web Site <https://llvm.org>`_.
33
34Note that if you are reading this file from a Git checkout or the
35main Clang web page, this document applies to the *next* release, not
36the current one. To see the release notes for a specific release, please
37see the `releases page <https://llvm.org/releases/>`_.
38
39What's New in Clang |release|?
40==============================
41
42Some of the major new features and improvements to Clang are listed
43here. Generic improvements to Clang as a whole or to its underlying
44infrastructure are described first, followed by language-specific
45sections with improvements to Clang's support for those languages.
46
47Major New Features
48------------------
49
50- Clang now supports the ``-fzero-call-used-regs`` feature for x86. The purpose
51  of this feature is to limit Return-Oriented Programming (ROP) exploits and
52  information leakage. It works by zeroing out a selected class of registers
53  before function return --- e.g., all GPRs that are used within the function.
54  There is an analogous ``zero_call_used_regs`` attribute to allow for finer
55  control of this feature.
56
57- Clang now supports randomizing structure layout in C. This feature is a
58  compile-time hardening technique, making it more difficult for an attacker to
59  retrieve data from structures. Specify randomization with the
60  ``randomize_layout`` attribute. The corresponding ``no_randomize_layout``
61  attribute can be used to turn the feature off.
62
63  A seed value is required to enable randomization, and is deterministic based
64  on a seed value. Use the ``-frandomize-layout-seed=`` or
65  ``-frandomize-layout-seed-file=`` flags.
66
67  .. note::
68
69      Randomizing structure layout is a C-only feature.
70
71- Experimental support for HLSL has been added. The implementation is
72  incomplete and highly experimental. For more information about the ongoing
73  work to support HLSL see the `documentation
74  <https://clang.llvm.org/docs/HLSLSupport.html>`_, or the `GitHub project
75  <https://github.com/orgs/llvm/projects/4>`_.
76
77Bug Fixes
78---------
79- ``CXXNewExpr::getArraySize()`` previously returned a ``llvm::Optional``
80  wrapping a ``nullptr`` when the ``CXXNewExpr`` did not have an array
81  size expression. This was fixed and ``::getArraySize()`` will now always
82  either return ``None`` or a ``llvm::Optional`` wrapping a valid ``Expr*``.
83  This fixes `Issue 53742 <https://github.com/llvm/llvm-project/issues/53742>`_.
84- We now ignore full expressions when traversing cast subexpressions. This
85  fixes `Issue 53044 <https://github.com/llvm/llvm-project/issues/53044>`_.
86- Allow ``-Wno-gnu`` to silence GNU extension diagnostics for pointer
87  arithmetic diagnostics. Fixes `Issue 54444
88  <https://github.com/llvm/llvm-project/issues/54444>`_.
89- Placeholder constraints, as in ``Concept auto x = f();``, were not checked
90  when modifiers like ``auto&`` or ``auto**`` were added. These constraints are
91  now checked.
92  This fixes  `Issue 53911 <https://github.com/llvm/llvm-project/issues/53911>`_
93  and  `Issue 54443 <https://github.com/llvm/llvm-project/issues/54443>`_.
94- Previously invalid member variables with template parameters would crash clang.
95  Now fixed by setting identifiers for them.
96  This fixes `Issue 28475 (PR28101) <https://github.com/llvm/llvm-project/issues/28475>`_.
97- Now allow the ``restrict`` and ``_Atomic`` qualifiers to be used in
98  conjunction with ``__auto_type`` to match the behavior in GCC. This fixes
99  `Issue 53652 <https://github.com/llvm/llvm-project/issues/53652>`_.
100- No longer crash when specifying a variably-modified parameter type in a
101  function with the ``naked`` attribute. This fixes
102  `Issue 50541 <https://github.com/llvm/llvm-project/issues/50541>`_.
103- Allow multiple ``#pragma weak`` directives to name the same undeclared (if an
104  alias, target) identifier instead of only processing one such ``#pragma weak``
105  per identifier.
106  Fixes `Issue 28985 <https://github.com/llvm/llvm-project/issues/28985>`_.
107- Assignment expressions in C11 and later mode now properly strip the _Atomic
108  qualifier when determining the type of the assignment expression. Fixes
109  `Issue 48742 <https://github.com/llvm/llvm-project/issues/48742>`_.
110- Improved the diagnostic when accessing a member of an atomic structure or
111  union object in C; was previously an unhelpful error, but now issues a
112  ``-Watomic-access`` warning which defaults to an error. Fixes
113  `Issue 54563 <https://github.com/llvm/llvm-project/issues/54563>`_.
114- Unevaluated lambdas in dependant contexts no longer result in clang crashing.
115  This fixes Issues `50376 <https://github.com/llvm/llvm-project/issues/50376>`_,
116  `51414 <https://github.com/llvm/llvm-project/issues/51414>`_,
117  `51416 <https://github.com/llvm/llvm-project/issues/51416>`_,
118  and `51641 <https://github.com/llvm/llvm-project/issues/51641>`_.
119- The builtin function __builtin_dump_struct would crash clang when the target
120  struct contains a bitfield. It now correctly handles bitfields.
121  This fixes Issue `Issue 54462 <https://github.com/llvm/llvm-project/issues/54462>`_.
122- Statement expressions are now disabled in default arguments in general.
123  This fixes Issue `Issue 53488 <https://github.com/llvm/llvm-project/issues/53488>`_.
124- According to `CWG 1394 <https://wg21.link/cwg1394>`_ and
125  `C++20 [dcl.fct.def.general]p2 <https://timsong-cpp.github.io/cppwp/n4868/dcl.fct.def#general-2.sentence-3>`_,
126  Clang should not diagnose incomplete types in function definitions if the function body is "= delete;".
127  This fixes Issue `Issue 52802 <https://github.com/llvm/llvm-project/issues/52802>`_.
128- Unknown type attributes with a ``[[]]`` spelling are no longer diagnosed twice.
129  This fixes Issue `Issue 54817 <https://github.com/llvm/llvm-project/issues/54817>`_.
130- Clang should no longer incorrectly diagnose a variable declaration inside of
131  a lambda expression that shares the name of a variable in a containing
132  if/while/for/switch init statement as a redeclaration.
133  This fixes `Issue 54913 <https://github.com/llvm/llvm-project/issues/54913>`_.
134- Overload resolution for constrained function templates could use the partial
135  order of constraints to select an overload, even if the parameter types of
136  the functions were different. It now diagnoses this case correctly as an
137  ambiguous call and an error. Fixes
138  `Issue 53640 <https://github.com/llvm/llvm-project/issues/53640>`_.
139- No longer crash when trying to determine whether the controlling expression
140  argument to a generic selection expression has side effects in the case where
141  the expression is result dependent. This fixes
142  `Issue 50227 <https://github.com/llvm/llvm-project/issues/50227>`_.
143- Fixed an assertion when constant evaluating an initializer for a GCC/Clang
144  floating-point vector type when the width of the initialization is exactly
145  the same as the elements of the vector being initialized.
146  Fixes `Issue 50216 <https://github.com/llvm/llvm-project/issues/50216>`_.
147- Fixed a crash when the ``__bf16`` type is used such that its size or
148  alignment is calculated on a target which does not support that type. This
149  fixes `Issue 50171 <https://github.com/llvm/llvm-project/issues/50171>`_.
150- Fixed a false positive diagnostic about an unevaluated expression having no
151  side effects when the expression is of VLA type and is an operand of the
152  ``sizeof`` operator. Fixes `Issue 48010 <https://github.com/llvm/llvm-project/issues/48010>`_.
153- Fixed a false positive diagnostic about scoped enumerations being a C++11
154  extension in C mode. A scoped enumeration's enumerators cannot be named in C
155  because there is no way to fully qualify the enumerator name, so this
156  "extension" was unintentional and useless. This fixes
157  `Issue 42372 <https://github.com/llvm/llvm-project/issues/42372>`_.
158- Clang will now find and emit a call to an allocation function in a
159  promise_type body for coroutines if there is any allocation function
160  declaration in the scope of promise_type. Additionally, to implement CWG2585,
161  a coroutine will no longer generate a call to a global allocation function
162  with the signature (std::size_t, p0, ..., pn).
163  This fixes Issue `Issue 54881 <https://github.com/llvm/llvm-project/issues/54881>`_.
164- Implement `CWG 2394 <https://wg21.link/cwg2394>`_: Const class members
165  may be initialized with a defaulted default constructor under the same
166  conditions it would be allowed for a const object elsewhere.
167- ``__has_unique_object_representations`` no longer reports that ``_BitInt`` types
168  have unique object representations if they have padding bits.
169- Unscoped and scoped enumeration types can no longer be initialized from a
170  brace-init-list containing a single element of a different scoped enumeration
171  type.
172- Allow use of an elaborated type specifier as a ``_Generic`` selection
173  association in C++ mode. This fixes
174  `Issue 55562 <https://github.com/llvm/llvm-project/issues/55562>`_.
175- Clang will allow calling a ``consteval`` function in a default argument. This
176  fixes `Issue 48230 <https://github.com/llvm/llvm-project/issues/48230>`_.
177- Fixed memory leak due to ``VarTemplateSpecializationDecl`` using
178  ``TemplateArgumentListInfo`` instead of ``ASTTemplateArgumentListInfo``.
179- An initializer for a static variable declaration, which is nested
180  inside a statement expression in an aggregate initializer, is now
181  emitted as a dynamic initializer. Previously the variable would
182  incorrectly be zero-initialized. In contexts where a dynamic
183  initializer is not allowed this is now diagnosed as an error.
184- Clang now correctly emits symbols for implicitly instantiated constexpr
185  template function. Fixes `Issue 55560 <https://github.com/llvm/llvm-project/issues/55560>`_.
186
187Improvements to Clang's diagnostics
188^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
189- ``-Wliteral-range`` will warn on floating-point equality comparisons with
190  constants that are not representable in a casted value. For example,
191  ``(float) f == 0.1`` is always false.
192- ``-Winline-namespace-reopened-noninline`` now takes into account that the
193  ``inline`` keyword must appear on the original but not necessarily all
194  extension definitions of an inline namespace and therefore points its note
195  at the original definition. This fixes `Issue 50794 (PR51452)
196  <https://github.com/llvm/llvm-project/issues/50794>`_.
197- ``-Wunused-but-set-variable`` now also warns if the variable is only used
198  by unary operators.
199- ``-Wunused-variable`` no longer warn for references extending the lifetime
200  of temporaries with side effects. This fixes `Issue 54489
201  <https://github.com/llvm/llvm-project/issues/54489>`_.
202- Modified the behavior of ``-Wstrict-prototypes`` and added a new, related
203  diagnostic ``-Wdeprecated-non-prototype``. The strict prototypes warning will
204  now only diagnose deprecated declarations and definitions of functions
205  without a prototype where the behavior in C2x will remain correct. This
206  diagnostic remains off by default but is now enabled via ``-pedantic`` due to
207  it being a deprecation warning. ``-Wstrict-prototypes`` has no effect in C2x
208  or when ``-fno-knr-functions`` is enabled. ``-Wdeprecated-non-prototype``
209  will diagnose cases where the deprecated declarations or definitions of a
210  function without a prototype will change behavior in C2x. Additionally, it
211  will diagnose calls which pass arguments to a function without a prototype.
212  This warning is enabled only when the ``-Wdeprecated-non-prototype`` option
213  is enabled at the function declaration site, which allows a developer to
214  disable the diagnostic for all callers at the point of declaration. This
215  diagnostic is grouped under the ``-Wstrict-prototypes`` warning group, but is
216  enabled by default. ``-Wdeprecated-non-prototype`` has no effect in C2x or
217  when ``-fno-knr-functions`` is enabled.
218- Clang now appropriately issues an error in C when a definition of a function
219  without a prototype and with no arguments is an invalid redeclaration of a
220  function with a prototype. e.g., ``void f(int); void f() {}`` is now properly
221  diagnosed.
222- The ``-Wimplicit-function-declaration`` warning diagnostic now defaults to
223  an error in C99 and later. Prior to C2x, it may be downgraded to a warning
224  with ``-Wno-error=implicit-function-declaration``, or disabled entirely with
225  ``-Wno-implicit-function-declaration``. As of C2x, support for implicit
226  function declarations has been removed, and the warning options will have no
227  effect.
228- The ``-Wimplicit-int`` warning diagnostic now defaults to an error in C99 and
229  later. Prior to C2x, it may be downgraded to a warning with
230  ``-Wno-error=implicit-int``, or disabled entirely with ``-Wno-implicit-int``.
231  As of C2x, support for implicit int has been removed, and the warning options
232  will have no effect. Specifying ``-Wimplicit-int`` in C89 mode will now issue
233  warnings instead of being a noop.
234- No longer issue a "declaration specifiers missing, defaulting to int"
235  diagnostic in C89 mode because it is not an extension in C89, it was valid
236  code. The diagnostic has been removed entirely as it did not have a
237  diagnostic group to disable it, but it can be covered wholly by
238  ``-Wimplicit-int``.
239- ``-Wmisexpect`` warns when the branch weights collected during profiling
240  conflict with those added by ``llvm.expect``.
241- ``-Wthread-safety-analysis`` now considers overloaded compound assignment and
242  increment/decrement operators as writing to their first argument, thus
243  requiring an exclusive lock if the argument is guarded.
244- ``-Wenum-conversion`` now warns on converting a signed enum of one type to an
245  unsigned enum of a different type (or vice versa) rather than
246  ``-Wsign-conversion``.
247- Added the ``-Wunreachable-code-generic-assoc`` diagnostic flag (grouped under
248  the ``-Wunreachable-code`` flag) which is enabled by default and warns the
249  user about ``_Generic`` selection associations which are unreachable because
250  the type specified is an array type or a qualified type.
251- Added the ``-Wgnu-line-marker`` diagnostic flag (grouped under the ``-Wgnu``
252  flag) which is a portability warning about use of GNU linemarker preprocessor
253  directives. Fixes `Issue 55067 <https://github.com/llvm/llvm-project/issues/55067>`_.
254- Using ``#elifdef`` and ``#elifndef`` that are incompatible with C/C++
255  standards before C2x/C++2b are now warned via ``-pedantic``. Additionally,
256  on such language mode, ``-Wpre-c2x-compat`` and ``-Wpre-c++2b-compat``
257  diagnostic flags report a compatibility issue.
258  Fixes `Issue 55306 <https://github.com/llvm/llvm-project/issues/55306>`_.
259- Clang now checks for stack resource exhaustion when recursively parsing
260  declarators in order to give a diagnostic before we run out of stack space.
261  This fixes `Issue 51642 <https://github.com/llvm/llvm-project/issues/51642>`_.
262- Unknown preprocessor directives in a skipped conditional block are now given
263  a typo correction suggestion if the given directive is sufficiently similar
264  to another preprocessor conditional directive. For example, if ``#esle``
265  appears in a skipped block, we will warn about the unknown directive and
266  suggest ``#else`` as an alternative. ``#elifdef`` and ``#elifndef`` are only
267  suggested when in C2x or C++2b mode. Fixes
268  `Issue 51598 <https://github.com/llvm/llvm-project/issues/51598>`_.
269- The ``-Wdeprecated`` diagnostic will now warn on out-of-line ``constexpr``
270  declarations downgraded to definitions in C++1z, in addition to the
271  existing warning on out-of-line ``const`` declarations.
272- ``-Wshift-overflow`` will not warn for signed left shifts in C++20 mode
273  (and newer), as it will always wrap and never overflow. This fixes
274  `Issue 52873 <https://github.com/llvm/llvm-project/issues/52873>`_.
275- When using class templates without arguments, clang now tells developers
276  that template arguments are missing in certain contexts.
277  This fixes `Issue 55962 <https://github.com/llvm/llvm-project/issues/55962>`_.
278- Printable Unicode characters within `static_assert` messages are no longer
279  escaped.
280- The ``-Winfinite-recursion`` diagnostic no longer warns about
281  unevaluated operands of a ``typeid`` expression, as they are now
282  modeled correctly in the CFG. This fixes
283  `Issue 21668 <https://github.com/llvm/llvm-project/issues/21668>`_.
284- ``-Wself-assign``, ``-Wself-assign-overloaded`` and ``-Wself-move`` will
285  suggest a fix if the decl being assigned is a parameter that shadows a data
286  member of the contained class.
287
288Non-comprehensive list of changes in this release
289-------------------------------------------------
290
291- Improve __builtin_dump_struct:
292
293  - Support bitfields in struct and union.
294  - Improve the dump format, dump both bitwidth(if its a bitfield) and field
295    value.
296  - Remove anonymous tag locations and flatten anonymous struct members.
297  - Beautify dump format, add indent for struct members.
298  - Support passing additional arguments to the formatting function, allowing
299    use with ``fprintf`` and similar formatting functions.
300  - Support use within constant evaluation in C++, if a ``constexpr``
301    formatting function is provided.
302  - Support formatting of base classes in C++.
303  - Support calling a formatting function template in C++, which can provide
304    custom formatting for non-aggregate types.
305
306- Previously disabled sanitizer options now enabled by default:
307  - ASAN_OPTIONS=detect_stack_use_after_return=1 (only on Linux).
308  - MSAN_OPTIONS=poison_in_dtor=1.
309
310New Compiler Flags
311------------------
312- Added the ``-fno-knr-functions`` flag to allow users to opt into the C2x
313  behavior where a function with an empty parameter list is treated as though
314  the parameter list were ``void``. There is no ``-fknr-functions`` or
315  ``-fno-no-knr-functions`` flag; this feature cannot be disabled in language
316  modes where it is required, such as C++ or C2x.
317- A new ARM pass to workaround Cortex-A57 Erratum 1742098 and Cortex-A72 Erratum
318  1655431 can be enabled using ``-mfix-cortex-a57-aes-1742098`` or
319  ``-mfix-cortex-a72-aes-1655431``. The pass is enabled when using either of
320  these cpus with ``-mcpu=`` and can be disabled using
321  ``-mno-fix-cortex-a57-aes-1742098`` or ``-mno-fix-cortex-a72-aes-1655431``.
322- Added the ``-fexperimental-max-bitint-width=`` option to increase the maximum
323  allowed bit width of ``_BitInt`` types beyond the default of 128 bits. Some
324  operations, such as division or float-to-integer conversion, on ``_BitInt``
325  types with more than 128 bits currently crash clang. This option will be
326  removed in the future once clang supports all such operations.
327- Added the ``-print-diagnostic-options`` option, which prints a list of
328  warnings the compiler supports.
329- Added the ``-Warray-parameter`` warning. It diagnoses differences between
330  array parameters between function redeclarations (arrays of different extents,
331  etc). This flag is related to the same flag in GCC, but is different in that
332  it does not accept an explicitly- specified warning level and use of this flag
333  has no effect on ``-Warray-bounds``.
334
335Deprecated Compiler Flags
336-------------------------
337
338Modified Compiler Flags
339-----------------------
340
341Removed Compiler Flags
342-------------------------
343- Removed the ``-fno-concept-satisfaction-caching`` flag. The flag was added
344  at the time when the draft of C++20 standard did not permit caching of
345  atomic constraints. The final standard permits such caching, see
346  `WG21 P2104R0 <http://wg21.link/p2104r0>`_.
347
348New Pragmas in Clang
349--------------------
350- Added support for MSVC's ``#pragma function``, which tells the compiler to
351  generate calls to functions listed in the pragma instead of using the
352  builtins.
353- Added support for MSVC's ``#pragma alloc_text``. The pragma names the code
354  section functions are placed in. The pragma only applies to functions with
355  C linkage.
356- Added support for an empty optimization list for MSVC's ``#pragma optimize``.
357  The pragma takes a list of optimizations to turn on or off which applies to
358  all functions following the pragma. At the moment, only an empty list is
359  supported.
360
361- ...
362
363Attribute Changes in Clang
364--------------------------
365
366- Added support for parameter pack expansion in ``clang::annotate``.
367
368- The ``overloadable`` attribute can now be written in all of the syntactic
369  locations a declaration attribute may appear.
370  This fixes `Issue 53805 <https://github.com/llvm/llvm-project/issues/53805>`_.
371
372- Improved namespace attributes handling:
373
374  - Handle GNU attributes before a namespace identifier and subsequent
375    attributes of different kinds.
376  - Emit error on GNU attributes for a nested namespace definition.
377
378- Statement attributes ``[[clang::noinline]]`` and  ``[[clang::always_inline]]``
379  can be used to control inlining decisions at callsites.
380
381- ``#pragma clang attribute push`` now supports multiple attributes within a single directive.
382
383- The ``__declspec(naked)`` attribute can no longer be written on a member
384  function in Microsoft compatibility mode, matching the behavior of cl.exe.
385
386- Attribute ``no_builtin`` should now affect the generated code. It now disables
387  builtins (corresponding to the specific names listed in the attribute) in the
388  body of the function the attribute is on.
389
390- When the ``weak`` attribute is applied to a const qualified variable clang no longer
391  tells the backend it is allowed to optimize based on initializer value.
392
393- Added the ``clang::annotate_type`` attribute, which can be used to add
394  annotations to types (see documentation for details).
395
396- Added half float to types that can be represented by ``__attribute__((mode(XX)))``.
397
398- The ``format`` attribute can now be applied to non-variadic functions. The
399  format string must correctly format the fixed parameter types of the function.
400  Using the attribute this way emits a GCC compatibility diagnostic.
401
402Windows Support
403---------------
404
405- Add support for MSVC-compatible ``/JMC``/``/JMC-`` flag in clang-cl (supports
406  X86/X64/ARM/ARM64). ``/JMC`` could only be used when ``/Zi`` or ``/Z7`` is
407  turned on. With this addition, clang-cl can be used in Visual Studio for the
408  JustMyCode feature. Note, you may need to manually add ``/JMC`` as additional
409  compile options in the Visual Studio since it currently assumes clang-cl does not support ``/JMC``.
410
411- Implemented generation of SEH unwind information on ARM. (C++ exception
412  handling in MSVC mode is still unimplemented though.)
413
414- Switched MinGW mode on ARM to use SEH instead of DWARF for unwind information.
415
416AIX Support
417-----------
418
419- The driver no longer adds ``-mignore-xcoff-visibility`` by default for AIX
420  targets when no other visibility command-line options are in effect, as
421  ignoring hidden visibility can silently have undesirable side effects (e.g
422  when libraries depend on visibility to hide non-ABI facing entities). The
423  ``-mignore-xcoff-visibility`` option can be manually specified on the
424  command-line to recover the previous behavior if desired.
425
426C Language Changes in Clang
427---------------------------
428
429C2x Feature Support
430-------------------
431
432- Implemented `WG14 N2674 The noreturn attribute <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2764.pdf>`_.
433- Implemented `WG14 N2935 Make false and true first-class language features <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2935.pdf>`_.
434- Implemented `WG14 N2763 Adding a fundamental type for N-bit integers <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2763.pdf>`_.
435- Implemented `WG14 N2775 Literal suffixes for bit-precise integers <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2775.pdf>`_.
436- Implemented the ``*_WIDTH`` macros to complete support for
437  `WG14 N2412 Two's complement sign representation for C2x <https://www9.open-std.org/jtc1/sc22/wg14/www/docs/n2412.pdf>`_.
438- Implemented `WG14 N2418 Adding the u8 character prefix <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2418.pdf>`_.
439- Removed support for implicit function declarations. This was a C89 feature
440  that was removed in C99, but cannot be supported in C2x because it requires
441  support for functions without prototypes, which no longer exist in C2x.
442- Implemented `WG14 N2841 No function declarators without prototypes <https://www9.open-std.org/jtc1/sc22/wg14/www/docs/n2841.htm>`_
443  and `WG14 N2432 Remove support for function definitions with identifier lists <https://www9.open-std.org/jtc1/sc22/wg14/www/docs/n2432.pdf>`_.
444
445C++ Language Changes in Clang
446-----------------------------
447
448- Improved ``-O0`` code generation for calls to ``std::move``, ``std::forward``,
449  ``std::move_if_noexcept``, ``std::addressof``, and ``std::as_const``. These
450  are now treated as compiler builtins and implemented directly, rather than
451  instantiating the definition from the standard library.
452- Fixed mangling of nested dependent names such as ``T::a::b``, where ``T`` is a
453  template parameter, to conform to the Itanium C++ ABI and be compatible with
454  GCC. This breaks binary compatibility with code compiled with earlier versions
455  of clang; use the ``-fclang-abi-compat=14`` option to get the old mangling.
456- Preprocessor character literals with a ``u8`` prefix are now correctly treated as
457  unsigned character literals. This fixes `Issue 54886 <https://github.com/llvm/llvm-project/issues/54886>`_.
458- Stopped allowing constraints on non-template functions to be compliant with
459  dcl.decl.general p4.
460
461C++20 Feature Support
462^^^^^^^^^^^^^^^^^^^^^
463- Diagnose consteval and constexpr issues that happen at namespace scope. This
464  partially addresses `Issue 51593 <https://github.com/llvm/llvm-project/issues/51593>`_.
465- No longer attempt to evaluate a consteval UDL function call at runtime when
466  it is called through a template instantiation. This fixes
467  `Issue 54578 <https://github.com/llvm/llvm-project/issues/54578>`_.
468
469- Implemented ``__builtin_source_location()``, which enables library support
470  for ``std::source_location``.
471
472- The mangling scheme for C++20 modules has incompatibly changed. The
473  initial mangling was discovered not to be reversible, and the weak
474  ownership design decision did not give the backwards compatibility
475  that was hoped for. C++20 since added ``extern "C++"`` semantics
476  that can be used for such compatibility. The demangler now demangles
477  symbols with named module attachment.
478
479- As per "Conditionally Trivial Special Member Functions" (P0848), it is
480  now possible to overload destructors using concepts. Note that the rest
481  of the paper about other special member functions is not yet implemented.
482
483C++2b Feature Support
484^^^^^^^^^^^^^^^^^^^^^
485
486- Implemented `P2128R6: Multidimensional subscript operator <https://wg21.link/P2128R6>`_.
487- Implemented `P0849R8: auto(x): decay-copy in the language <https://wg21.link/P0849R8>`_.
488- Implemented `P2242R3: Non-literal variables (and labels and gotos) in constexpr functions	<https://wg21.link/P2242R3>`_.
489
490CUDA/HIP Language Changes in Clang
491----------------------------------
492
493- Added `__noinline__` as a keyword to avoid diagnostics due to usage of
494  `__attribute__((__noinline__))` in CUDA/HIP programs.
495
496Objective-C Language Changes in Clang
497-------------------------------------
498
499OpenCL C Language Changes in Clang
500----------------------------------
501
502...
503
504ABI Changes in Clang
505--------------------
506
507- GCC doesn't pack non-POD members in packed structs unless the packed
508  attribute is also specified on the member. Clang historically did perform
509  such packing. Clang now matches the gcc behavior (except on Darwin and PS4).
510  You can switch back to the old ABI behavior with the flag:
511  ``-fclang-abi-compat=14.0``.
512- When compiling C for ARM or AArch64, a zero-length bitfield in a ``struct``
513  (e.g. ``int : 0``) no longer prevents the structure from being considered a
514  homogeneous floating-point or vector aggregate. The new behavior agrees with
515  the AAPCS specification, and matches the similar bug fix in GCC 12.1.
516- Targeting AArch64, since D127209 LLVM now only preserves the z8-z23
517  and p4-p15 registers across a call if the registers z0-z7 or p0-p3 are
518  used to pass data into or out of a subroutine. The new behavior
519  matches the AAPCS. Previously LLVM preserved z8-z23 and p4-p15 across
520  a call if the callee had an SVE type anywhere in its signature. This
521  would cause an incorrect use of the caller-preserved z8-z23 and p4-p15
522  ABI for example if the 9th argument or greater were the first SVE type
523  in the signature of a function.
524- All copy constructors can now be trivial if they are not user-provided,
525  regardless of the type qualifiers of the argument of the defaulted constructor,
526  fixing dr2171.
527  You can switch back to the old ABI behavior with the flag:
528  ``-fclang-abi-compat=14.0``.
529
530OpenMP Support in Clang
531-----------------------
532
533...
534
535CUDA Support in Clang
536---------------------
537
538- ...
539
540X86 Support in Clang
541--------------------
542
543- Support ``-mharden-sls=[none|all|return|indirect-jmp]`` for straight-line
544  speculation hardening.
545- Support for the ``_Float16`` type has been added for all targets with SSE2.
546  When AVX512-FP16 is not available, arithmetic on ``_Float16`` is emulated
547  using ``float``.
548- Added the ``-m[no-]rdpru`` flag to enable/disable the RDPRU instruction
549  provided by AMD Zen2 and later processors. Defined intrinsics for using
550  this instruction (see rdpruintrin.h).
551
552DWARF Support in Clang
553----------------------
554
555- clang now adds DWARF information for inline strings in C/C++ programs,
556  allowing ``line:column`` symbolization of strings. Some debugging programs may
557  require updating, as this takes advantage of DWARF ``DW_TAG_variable``
558  structures *without* a ``DW_AT_name`` field, which is valid DWARF, but may be
559  handled incorrectly by some software (e.g. new failures with incorrect
560  assertions).
561
562Arm and AArch64 Support in Clang
563--------------------------------
564
565- clang now supports the Cortex-M85 CPU, which can be chosen with
566  `-mcpu=cortex-m85`. By default, this has PACBTI turned on, but it can be
567  disabled with `-mcpu=cortex-m85+nopacbti`.
568
569Floating Point Support in Clang
570-------------------------------
571
572Internal API Changes
573--------------------
574
575- Added a new attribute flag ``AcceptsExprPack`` that when set allows
576  expression pack expansions in the parsed arguments of the corresponding
577  attribute. Additionally it introduces delaying of attribute arguments, adding
578  common handling for creating attributes that cannot be fully initialized
579  prior to template instantiation.
580
581Build System Changes
582--------------------
583
584* CMake ``-DCLANG_DEFAULT_PIE_ON_LINUX=ON`` is now the default. This is used by
585  linux-gnu systems to decide whether ``-fPIE -pie`` is the default (instead of
586  ``-fno-pic -no-pie``). This matches GCC installations on many Linux distros.
587  Note: linux-android and linux-musl always default to ``-fPIE -pie``, ignoring
588  this variable. ``-DCLANG_DEFAULT_PIE_ON_LINUX`` may be removed in the future.
589
590AST Matchers
591------------
592
593- Expanded ``isInline`` narrowing matcher to support C++17 inline variables.
594
595- Added ``forEachTemplateArgument`` matcher which creates a match every
596  time a ``templateArgument`` matches the matcher supplied to it.
597
598- Added ``objcStringLiteral`` matcher which matches ObjectiveC String
599  literal expressions.
600
601clang-format
602------------
603
604- **Important change**: Renamed ``IndentRequires`` to ``IndentRequiresClause``
605  and changed the default for all styles from ``false`` to ``true``.
606
607- Reworked and improved handling of concepts and requires. Added the
608  ``RequiresClausePosition`` option as part of that.
609
610- Changed ``BreakBeforeConceptDeclarations`` from ``Boolean`` to an enum.
611
612- Option ``InsertBraces`` has been added to insert optional braces after control
613  statements.
614
615clang-extdef-mapping
616--------------------
617
618- clang-extdef-mapping now accepts .ast files as input. This is faster than to
619  recompile the files from sources when extracting method definitons. This can
620  be really beneficial when creating .ast files for input to the clang-static-analyzer.
621
622libclang
623--------
624
625- ...
626
627Static Analyzer
628---------------
629- `New CTU implementation
630  <https://discourse.llvm.org/t/rfc-much-faster-cross-translation-unit-ctu-analysis-implementation/61728>`_
631  that keeps the slow-down around 2x compared to the single-TU analysis, even
632  in case of complex C++ projects. Still, it finds the majority of the "old"
633  CTU findings. Besides, not more than ~3% of the bug reports are lost compared
634  to single-TU analysis, the lost reports are highly likely to be false
635  positives.
636
637- Added a new checker ``alpha.unix.cstring.UninitializedRead`` this will check for uninitialized reads
638  from common memory copy/manipulation functions such as ``memcpy``, ``mempcpy``, ``memmove``, ``memcmp``, `
639  `strcmp``, ``strncmp``, ``strcpy``, ``strlen``, ``strsep`` and many more. Although
640  this checker currently is in list of alpha checkers due to a false positive.
641
642- Added a new checker ``alpha.unix.Errno``. This can find the first read
643  of ``errno`` after successful standard function calls, such use of ``errno``
644  could be unsafe.
645
646- Deprecate the ``-analyzer-store region`` and
647  ``-analyzer-opt-analyze-nested-blocks`` analyzer flags.
648  These flags are still accepted, but a warning will be displayed.
649  These flags will be rejected, thus turned into a hard error starting with
650  ``clang-16``.
651
652.. _release-notes-ubsan:
653
654Undefined Behavior Sanitizer (UBSan)
655------------------------------------
656
657Core Analysis Improvements
658==========================
659
660- ...
661
662New Issues Found
663================
664
665- ...
666
667Python Binding Changes
668----------------------
669
670The following methods have been added:
671
672-  ...
673
674Significant Known Problems
675==========================
676
677Additional Information
678======================
679
680A wide variety of additional information is available on the `Clang web
681page <https://clang.llvm.org/>`_. The web page contains versions of the
682API documentation which are up-to-date with the Git version of
683the source code. You can access versions of these documents specific to
684this release by going into the "``clang/docs/``" directory in the Clang
685tree.
686
687If you have any questions or comments about Clang, please feel free to
688contact us on the Discourse forums (Clang Frontend category)
689<https://discourse.llvm.org/c/clang/6>`_.
690