maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/docs/ReleaseNotes.rst

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

200 lines
6.0 KiB
ReStructuredText
Raw Normal View History

[docs] Remove hard-coded version numbers from sphinx configs This updates all the non-runtime project release notes to use the version number from CMake instead of the hard-coded version numbers in conf.py. It also hides warnings about pre-releases when the git suffix is dropped from the LLVM version in CMake. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D112181
2022-02-02 15:13:01 +08:00
============================
LLVM |release| Release Notes
============================
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
.. contents::
:local:
[docs] Remove hard-coded version numbers from sphinx configs This updates all the non-runtime project release notes to use the version number from CMake instead of the hard-coded version numbers in conf.py. It also hides warnings about pre-releases when the git suffix is dropped from the LLVM version in CMake. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D112181
2022-02-02 15:13:01 +08:00
.. only:: PreRelease
.. warning::
These are in-progress notes for the upcoming LLVM |version| release.
Release notes for previous releases can be found on
`the Download Page <https://releases.llvm.org/download.html>`_.
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
Introduction
============
This document contains the release notes for the LLVM Compiler Infrastructure,
[docs] Remove hard-coded version numbers from sphinx configs This updates all the non-runtime project release notes to use the version number from CMake instead of the hard-coded version numbers in conf.py. It also hides warnings about pre-releases when the git suffix is dropped from the LLVM version in CMake. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D112181
2022-02-02 15:13:01 +08:00
release |release|. Here we describe the status of LLVM, including major improvements
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
from the previous release, improvements in various subprojects of LLVM, and
some of the current users of the code. All LLVM releases may be downloaded
ReleaseNotes: update links to use https llvm-svn: 341785
2018-09-10 16:50:31 +08:00
from the `LLVM releases web site <https://llvm.org/releases/>`_.
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
For more information about LLVM, including information about the latest
ReleaseNotes: update links to use https llvm-svn: 341785
2018-09-10 16:50:31 +08:00
release, please check out the `main LLVM web site <https://llvm.org/>`_. If you
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
have questions or comments, the `LLVM Developer's Mailing List
ReleaseNotes: update links to use https llvm-svn: 341785
2018-09-10 16:50:31 +08:00
<https://lists.llvm.org/mailman/listinfo/llvm-dev>`_ is a good place to send
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
them.
Bump the trunk major version to 11 and clear the release notes.
2020-01-15 17:02:56 +08:00
Note that if you are reading this file from a Git checkout or the main
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
LLVM 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
ReleaseNotes: update links to use https llvm-svn: 341785
2018-09-10 16:50:31 +08:00
page <https://llvm.org/releases/>`_.
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
docs: Nuke the old release notes. This change also removes a bunch of boilerplate and stuffing which made it unnecessarily hard to navigate and see the comparatively miniscule actual content that was added to this document during the 3.2 development period (or maybe even sticking around from earlier releases...). The new organization (a flat list) optimizes for making it easy for people who know about changes to add them to the document. It's completely trivial for anyone with basic knowledge of LLVM to come in later (such as when preparing for the actual release) and cluster any changes into logical groups. However, I have left some comments indicating how to add larger descriptions, if someone is feeling adventurous ;) Hopefully this organization will highlight how little effort is being put into producing accurate, high-quality release notes, prompting a corresponding improvement for the 3.3 release. I have preserved the changes to this document that are not present in the 3.2 release notes. There were only two... I'm pretty sure we've been busier than that... (version control shows +213347/-173656 raw lines just in the LLVM repo since the 3.2 release). llvm-svn: 172954
2013-01-20 11:29:50 +08:00
Non-comprehensive list of changes in this release
=================================================
.. NOTE
For small 1-3 sentence descriptions, just add an entry at the end of
this list. If your description won't fit comfortably in one bullet
point (e.g. maybe you would like to give an example of the
functionality, or simply have a lot to talk about), see the `NOTE` below
for adding a new subsection.
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
[cmake] Remove LLVM_{BUILD,LINK}_LLVM_DYLIB options on Windows Summary: The options aren't supported so they can be removed. Reviewers: beanz, smeenai, compnerd Reviewed By: compnerd Subscribers: mgorny, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D69877
2019-11-09 02:05:37 +08:00
docs: Nuke the old release notes. This change also removes a bunch of boilerplate and stuffing which made it unnecessarily hard to navigate and see the comparatively miniscule actual content that was added to this document during the 3.2 development period (or maybe even sticking around from earlier releases...). The new organization (a flat list) optimizes for making it easy for people who know about changes to add them to the document. It's completely trivial for anyone with basic knowledge of LLVM to come in later (such as when preparing for the actual release) and cluster any changes into logical groups. However, I have left some comments indicating how to add larger descriptions, if someone is feeling adventurous ;) Hopefully this organization will highlight how little effort is being put into producing accurate, high-quality release notes, prompting a corresponding improvement for the 3.3 release. I have preserved the changes to this document that are not present in the 3.2 release notes. There were only two... I'm pretty sure we've been busier than that... (version control shows +213347/-173656 raw lines just in the LLVM repo since the 3.2 release). llvm-svn: 172954
2013-01-20 11:29:50 +08:00
.. NOTE
If you would like to document a larger change, then you can add a
subsection about it right here. You can copy the following boilerplate
and un-indent it (the indentation causes it to be inside this comment).
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
docs: Nuke the old release notes. This change also removes a bunch of boilerplate and stuffing which made it unnecessarily hard to navigate and see the comparatively miniscule actual content that was added to this document during the 3.2 development period (or maybe even sticking around from earlier releases...). The new organization (a flat list) optimizes for making it easy for people who know about changes to add them to the document. It's completely trivial for anyone with basic knowledge of LLVM to come in later (such as when preparing for the actual release) and cluster any changes into logical groups. However, I have left some comments indicating how to add larger descriptions, if someone is feeling adventurous ;) Hopefully this organization will highlight how little effort is being put into producing accurate, high-quality release notes, prompting a corresponding improvement for the 3.3 release. I have preserved the changes to this document that are not present in the 3.2 release notes. There were only two... I'm pretty sure we've been busier than that... (version control shows +213347/-173656 raw lines just in the LLVM repo since the 3.2 release). llvm-svn: 172954
2013-01-20 11:29:50 +08:00
Special New Feature
-------------------
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
docs: Nuke the old release notes. This change also removes a bunch of boilerplate and stuffing which made it unnecessarily hard to navigate and see the comparatively miniscule actual content that was added to this document during the 3.2 development period (or maybe even sticking around from earlier releases...). The new organization (a flat list) optimizes for making it easy for people who know about changes to add them to the document. It's completely trivial for anyone with basic knowledge of LLVM to come in later (such as when preparing for the actual release) and cluster any changes into logical groups. However, I have left some comments indicating how to add larger descriptions, if someone is feeling adventurous ;) Hopefully this organization will highlight how little effort is being put into producing accurate, high-quality release notes, prompting a corresponding improvement for the 3.3 release. I have preserved the changes to this document that are not present in the 3.2 release notes. There were only two... I'm pretty sure we've been busier than that... (version control shows +213347/-173656 raw lines just in the LLVM repo since the 3.2 release). llvm-svn: 172954
2013-01-20 11:29:50 +08:00
Makes programs 10x faster by doing Special New Thing.
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
Bump the trunk major version to 14 and clear the release notes.
2021-07-28 12:51:07 +08:00
* ...
Ignore "no-frame-pointer-elim" and "no-frame-pointer-elim-non-leaf" in favor of "frame-pointer" D56351 (included in LLVM 8.0.0) introduced "frame-pointer". All tests which use "no-frame-pointer-elim" or "no-frame-pointer-elim-non-leaf" have been migrated to use "frame-pointer". Implement UpgradeFramePointerAttributes to upgrade the two obsoleted function attributes for bitcode. Their semantics are ignored. Differential Revision: https://reviews.llvm.org/D71863
2019-12-25 10:12:15 +08:00
Added 2 notes 1) Skylake and KNL support for X86 2) masked intrinsics load/store/gather/scatter Differential Revision: http://reviews.llvm.org/D18353 llvm-svn: 264703
2016-03-29 14:55:56 +08:00
Changes to the LLVM IR
----------------------
[docs] Mention that the legacy PM is deprecated and will be removed after 14 Per https://lists.llvm.org/pipermail/llvm-dev/2021-August/152305.html. Reviewed By: MaskRay, fhahn Differential Revision: https://reviews.llvm.org/D109080
2021-09-02 02:53:53 +08:00
* Using the legacy pass manager for the optimization pipeline is deprecated and
will be removed after LLVM 14. In the meantime, only minimal effort will be
made to maintain the legacy pass manager for the optimization pipeline.
[IR] Reduce max supported integer from 2^24-1 to 2^23. SelectionDAG will promote illegal types up to a power of 2 before splitting down to a legal type. This will create an IntegerType with a bit width that must be <= MAX_INT_BITS. This places an effective upper limit on any type of 2^23 so that we don't try create a 2^24 type. I considered putting a fatal error somewhere in the path from TargetLowering::getTypeConversion down to IntegerType::get, but limiting the type in IR seemed better. This breaks backwards compatibility with IR that is using a really large type. I suspect such IR is going to be very rare due to the the compile time costs such a type likely incurs. Prevents the ICE in PR51829. Reviewed By: efriedma, aaron.ballman Differential Revision: https://reviews.llvm.org/D109721
2021-09-14 22:33:33 +08:00
* Max allowed integer type was reduced from 2^24-1 bits to 2^23 bits.
[docs] Mention in release notes that we now support 2^32 alignment Missed in D110451. Reviewed By: hans Differential Revision: https://reviews.llvm.org/D111472
2021-10-12 01:19:43 +08:00
* Max allowed alignment was increased from 2^29 to 2^32.
[IR] Introduce the opaque pointer type The opaque pointer type is essentially just a normal pointer type with a null pointee type. This also adds support for the opaque pointer type to the bitcode reader/writer, as well as to textual IR. To avoid confusion with existing pointer types, we disallow creating a pointer to an opaque pointer. Opaque pointer types should not be widely used at this point since many parts of LLVM still do not support them. The next steps are to add some very simple use cases of opaque pointers to make sure they work, then start pretending that all pointers are opaque pointers and see what breaks. https://lists.llvm.org/pipermail/llvm-dev/2021-May/150359.html Reviewed By: dblaikie, dexonsmith, pcc Differential Revision: https://reviews.llvm.org/D101704
2021-05-02 10:04:42 +08:00
Retire VS2015 Support As proposed here: https://lists.llvm.org/pipermail/llvm-dev/2019-June/133147.html This patch raises the minimum supported version to build LLVM/Clang to Visual Studio 2017. Differential Revision: https://reviews.llvm.org/D64326 llvm-svn: 365452
2019-07-09 18:10:48 +08:00
Changes to building LLVM
------------------------
Raise the minimum Visual Studio version to VS2019 As raised here: https://lists.llvm.org/pipermail/llvm-dev/2021-November/153881.html Now that VS2022 is on general release, LLVM is expected to build on VS2017, VS2019 and VS2022, which is proving hazardous to maintain due to changes in behaviour including preprocessor and constexpr changes. Plus of the few developers that work with VS, many have already moved to VS2019/22. This patch proposes to raise the minimum supported version to VS2019 (16.x) - I've made the hard limit 16.0 or later, with the soft limit VS2019 16.7 - older versions of VS2019 are "allowed" (at your own risk) via the LLVM_FORCE_USE_OLD_TOOLCHAIN cmake flag. Differential Revision: https://reviews.llvm.org/D114639
2022-01-29 18:56:41 +08:00
* Building LLVM with Visual Studio now requires version 2019 or later.
[cmake] Add support for multiple distributions LLVM's build system contains support for configuring a distribution, but it can often be useful to be able to configure multiple distributions (e.g. if you want separate distributions for the tools and the libraries). Add this support to the build system, along with documentation and usage examples. Reviewed By: phosek Differential Revision: https://reviews.llvm.org/D89177
2020-10-02 05:35:28 +08:00
Replace TableGen range piece punctuator with '...' The TableGen range piece punctuator is currently '-' (e.g., {0-9}), which interacts oddly with the fact that an integer literal's sign is part of the literal. This patch replaces the '-' with the new punctuator '...'. The '-' punctuator is deprecated. Differential Revision: https://reviews.llvm.org/D85585 Change-Id: I3d53d14e23f878b142d8f84590dd465a0fb6c09c
2020-08-22 05:22:06 +08:00
Changes to TableGen
-------------------
[Aarch64] Adding support for Armv9-A Realm Management Extension This adds support for Armv9-A's Realm Management Extension, including three new system registers - MFAR_EL3, GPCCR_EL3 and GPTBR_EL3 - and four new TLBI instructions. The reference for the Realm Management Extension can be found at: https://developer.arm.com/documentation/ddi0615/aa. Based on patches by Victor Campos. Reviewed By: dmgreen Differential Revision: https://reviews.llvm.org/D104773
2021-06-22 23:43:36 +08:00
Changes to the AArch64 Backend
[NFC] Fixing short title underline in release notes file
2021-06-28 20:51:27 +08:00
------------------------------
[Aarch64] Adding support for Armv9-A Realm Management Extension This adds support for Armv9-A's Realm Management Extension, including three new system registers - MFAR_EL3, GPCCR_EL3 and GPTBR_EL3 - and four new TLBI instructions. The reference for the Realm Management Extension can be found at: https://developer.arm.com/documentation/ddi0615/aa. Based on patches by Victor Campos. Reviewed By: dmgreen Differential Revision: https://reviews.llvm.org/D104773
2021-06-22 23:43:36 +08:00
[docs] List support for Armv9-A, Armv9.1-A and Armv9.2-A in LLVM and Clang Reviewed By: pratlucas Differential Revision: https://reviews.llvm.org/D110241
2021-10-12 15:41:07 +08:00
* Added support for the Armv9-A, Armv9.1-A and Armv9.2-A architectures.
[AArch64] Always add -tune-cpu argument to -cc1 driver This patch ensures that we always tune for a given CPU on AArch64 targets when the user specifies the "-mtune=xyz" flag. In the AArch64Subtarget if the tune flag is unset we use the CPU value instead. I've updated the release notes here: llvm/docs/ReleaseNotes.rst and added tests here: clang/test/Driver/aarch64-mtune.c Differential Revision: https://reviews.llvm.org/D110258
2021-09-22 21:56:30 +08:00
* The compiler now recognises the "tune-cpu" function attribute to support
Fix documentation errors introduced by 607fb1bb8c91a2f284d8c63f3066ab8cc1a66955
2021-10-19 22:11:05 +08:00
the use of the -mtune frontend flag. This allows certain scheduling features
and optimisations to be enabled independently of the architecture. If the
"tune-cpu" attribute is absent it tunes according to the "target-cpu".
[Aarch64] Adding support for Armv9-A Realm Management Extension This adds support for Armv9-A's Realm Management Extension, including three new system registers - MFAR_EL3, GPCCR_EL3 and GPTBR_EL3 - and four new TLBI instructions. The reference for the Realm Management Extension can be found at: https://developer.arm.com/documentation/ddi0615/aa. Based on patches by Victor Campos. Reviewed By: dmgreen Differential Revision: https://reviews.llvm.org/D104773
2021-06-22 23:43:36 +08:00
Add IAS/EHABI changes to release notes llvm-svn: 204134
2014-03-18 18:16:15 +08:00
Changes to the ARM Backend
--------------------------
[docs] List support for Armv9-A, Armv9.1-A and Armv9.2-A in LLVM and Clang Reviewed By: pratlucas Differential Revision: https://reviews.llvm.org/D110241
2021-10-12 15:41:07 +08:00
* Added support for the Armv9-A, Armv9.1-A and Armv9.2-A architectures.
Add PACBTI-M support to LLVM release notes. Clang release note changes will be added once the last PACBTI-M command line patch lands. Reviewed By: vhscampos Differential Revision: https://reviews.llvm.org/D115507
2021-12-10 19:52:09 +08:00
* Added support for the Armv8.1-M PACBTI-M extension.
Clear the llvm release notes to make room for 3.6. llvm-svn: 216292
2014-08-23 05:57:38 +08:00
Added release notes for MIPS. llvm-svn: 213749
2014-07-23 20:59:26 +08:00
Changes to the MIPS Target
--------------------------
Bump the trunk major version to 11 and clear the release notes.
2020-01-15 17:02:56 +08:00
During this release ...
Added release notes for the Mips target. llvm-svn: 225607
2015-01-11 18:34:52 +08:00
Add entry about Hexagon V68 support to the release notes
2021-05-13 21:25:04 +08:00
Changes to the Hexagon Target
Fix section title underlining in the release notes
2021-05-13 21:36:07 +08:00
-----------------------------
Add entry about Hexagon V68 support to the release notes
2021-05-13 21:25:04 +08:00
Bump the trunk major version to 14 and clear the release notes.
2021-07-28 12:51:07 +08:00
* ...
Added release notes for MIPS. llvm-svn: 213749
2014-07-23 20:59:26 +08:00
Add PowerPC release notes for 3.5. Here's my take on 3.5 changes for PowerPC. Others please feel free to add, edit, delete as desired. Thanks, Bill llvm-svn: 214403
2014-07-31 22:38:17 +08:00
Changes to the PowerPC Target
Wrong heading level for PowerPC changes in release notes Oops. Used the wrong heading level by mistake. Thanks, Bill llvm-svn: 214405
2014-07-31 23:20:30 +08:00
-----------------------------
Add PowerPC release notes for 3.5. Here's my take on 3.5 changes for PowerPC. Others please feel free to add, edit, delete as desired. Thanks, Bill llvm-svn: 214403
2014-07-31 22:38:17 +08:00
Bump the trunk major version to 11 and clear the release notes.
2020-01-15 17:02:56 +08:00
During this release ...
Add PowerPC release notes for 3.5. Here's my take on 3.5 changes for PowerPC. Others please feel free to add, edit, delete as desired. Thanks, Bill llvm-svn: 214403
2014-07-31 22:38:17 +08:00
[Cygwin] Enable TLS as emutls. It resolves clang selfhosting with std::once() for Cygwin. FIXME: It may be EmulatedTLS-generic also for X86-Android. FIXME: Pass EmulatedTLS to LLVM CodeGen from Clang with -femulated-tls. llvm-svn: 256134
2015-12-21 10:37:23 +08:00
Changes to the X86 Target
Added 2 notes 1) Skylake and KNL support for X86 2) masked intrinsics load/store/gather/scatter Differential Revision: http://reviews.llvm.org/D18353 llvm-svn: 264703
2016-03-29 14:55:56 +08:00
-------------------------
[Cygwin] Enable TLS as emutls. It resolves clang selfhosting with std::once() for Cygwin. FIXME: It may be EmulatedTLS-generic also for X86-Android. FIXME: Pass EmulatedTLS to LLVM CodeGen from Clang with -femulated-tls. llvm-svn: 256134
2015-12-21 10:37:23 +08:00
Bump the trunk major version to 11 and clear the release notes.
2020-01-15 17:02:56 +08:00
During this release ...
[X86] AVX512FP16 instructions enabling 1/6 1. Enable FP16 type support and basic declarations used by following patches. 2. Enable new instructions VMOVW and VMOVSH. Ref.: https://software.intel.com/content/www/us/en/develop/download/intel-avx512-fp16-architecture-specification.html Reviewed By: LuoYuanke Differential Revision: https://reviews.llvm.org/D105263
2021-08-10 11:18:40 +08:00
* Support for ``AVX512-FP16`` instructions has been added.
AMDGPU: Note mesa version in release notes llvm-svn: 258784
2016-01-26 12:29:15 +08:00
Changes to the AMDGPU Target
-----------------------------
Bump the trunk major version to 12 and clear the release notes.
2020-07-15 17:40:53 +08:00
During this release ...
AMDGPU: Assume f32 denormals are enabled by default This will likely introduce catastrophic performance regressions on older subtargets, but should be correct. A follow up change will remove the old fp32-denormals subtarget features, and switch to using the new denormal-fp-math/denormal-fp-math-f32 attributes. Frontends should be making sure to add the denormal-fp-math-f32 attribute when appropriate to avoid performance regressions.
2019-11-01 14:32:31 +08:00
[ReleaseNotes] Mention the completion of the upstreaming of the AVR backend llvm-svn: 287273
2016-11-18 06:26:09 +08:00
Changes to the AVR Target
-----------------------------
Bump the trunk major version to 12 and clear the release notes.
2020-07-15 17:40:53 +08:00
During this release ...
[ReleaseNotes] Mention the completion of the upstreaming of the AVR backend llvm-svn: 287273
2016-11-18 06:26:09 +08:00
[WebAssembly] Add a release notes blurb Bid farewell to LLVM_EXPERIMENTAL_TARGETS_TO_BUILD! Differential Revision: https://reviews.llvm.org/D56648 llvm-svn: 351083
2019-01-15 02:20:30 +08:00
Changes to the WebAssembly Target
---------------------------------
Bump the trunk major version to 12 and clear the release notes.
2020-07-15 17:40:53 +08:00
During this release ...
[WebAssembly] Add a release notes blurb Bid farewell to LLVM_EXPERIMENTAL_TARGETS_TO_BUILD! Differential Revision: https://reviews.llvm.org/D56648 llvm-svn: 351083
2019-01-15 02:20:30 +08:00
Update release notes wrt OCaml bindings. llvm-svn: 225779
2015-01-13 17:48:02 +08:00
Changes to the OCaml bindings
-----------------------------
Add a C API section to the release notes. llvm-svn: 306777
2017-06-30 09:17:45 +08:00
Changes to the C API
--------------------
Recommit "[DWARF5]Addition of alignment atrribute in typedef DIE." This revision is revised to update Go-bindings and Release Notes. The original commit message follows. This patch, adds support for DW_AT_alignment[DWARF5] attribute, to be emitted with typdef DIE. When explicit alignment is specified. Patch by Awanish Pandey <Awanish.Pandey@amd.com> Reviewers: aprantl, dblaikie, jini.susan.george, SouraVX, alok, deadalinx Differential Revision: https://reviews.llvm.org/D70111
2019-12-03 11:59:54 +08:00
[LLVM-C]Add LLVMAddMetadataToInst, deprecated LLVMSetInstDebugLocation. IRBuilder has been updated to support preserving metdata in a more general manner. This patch adds `LLVMAddMetadataToInst` and deprecates `LLVMSetInstDebugLocation` in favor of the more general function. Reviewed By: aprantl Differential Revision: https://reviews.llvm.org/D93454
2021-10-22 18:00:23 +08:00
* ``LLVMSetInstDebugLocation`` has been deprecated in favor of the more general
``LLVMAddMetadataToInst``.
Recommit "[DWARF5]Addition of alignment atrribute in typedef DIE." This revision is revised to update Go-bindings and Release Notes. The original commit message follows. This patch, adds support for DW_AT_alignment[DWARF5] attribute, to be emitted with typdef DIE. When explicit alignment is specified. Patch by Awanish Pandey <Awanish.Pandey@amd.com> Reviewers: aprantl, dblaikie, jini.susan.george, SouraVX, alok, deadalinx Differential Revision: https://reviews.llvm.org/D70111
2019-12-03 11:59:54 +08:00
Changes to the Go bindings
--------------------------
Add a C API section to the release notes. llvm-svn: 306777
2017-06-30 09:17:45 +08:00
Remove the BBVectorize pass. It served us well, helped kick-start much of the vectorization efforts in LLVM, etc. Its time has come and past. Back in 2014: http://lists.llvm.org/pipermail/llvm-dev/2014-November/079091.html Time to actually let go and move forward. =] I've updated the release notes both about the removal and the deprecation of the corresponding C API. llvm-svn: 306797
2017-06-30 15:09:08 +08:00
[FastISel] Remove kill tracking This is a followup to D98145: As far as I know, tracking of kill flags in FastISel is just a compile-time optimization. However, I'm not actually seeing any compile-time regression when removing the tracking. This probably used to be more important in the past, before FastRA was switched to allocate instructions in reverse order, which means that it discovers kills as a matter of course. As such, the kill tracking doesn't really seem to serve a purpose anymore, and just adds additional complexity and potential for errors. This patch removes it entirely. The primary changes are dropping the hasTrivialKill() method and removing the kill arguments from the emitFast methods. The rest is mechanical fixup. Differential Revision: https://reviews.llvm.org/D98294
2021-03-10 04:04:03 +08:00
Changes to the FastISel infrastructure
--------------------------------------
Bump the trunk major version to 14 and clear the release notes.
2021-07-28 12:51:07 +08:00
* ...
[FastISel] Remove kill tracking This is a followup to D98145: As far as I know, tracking of kill flags in FastISel is just a compile-time optimization. However, I'm not actually seeing any compile-time regression when removing the tracking. This probably used to be more important in the past, before FastRA was switched to allocate instructions in reverse order, which means that it discovers kills as a matter of course. As such, the kill tracking doesn't really seem to serve a purpose anymore, and just adds additional complexity and potential for errors. This patch removes it entirely. The primary changes are dropping the hasTrivialKill() method and removing the kill arguments from the emitFast methods. The rest is mechanical fixup. Differential Revision: https://reviews.llvm.org/D98294
2021-03-10 04:04:03 +08:00
Set ADDE/ADDC/SUBE/SUBC to expand by default Summary: They've been deprecated in favor of UADDO/ADDCARRY or USUBO/SUBCARRY for a while. Target that uses these opcodes are changed in order to ensure their behavior doesn't change. Reviewers: efriedma, craig.topper, dblaikie, bkramer Subscribers: jholewinski, arsenm, jyknight, sdardis, nemanjai, nhaehnle, kbarton, fedor.sergeev, asb, rbar, johnrusso, simoncook, jordy.potman.lists, apazos, sabuasal, niosHD, jrtc27, zzheng, edward-jones, mgrang, atanasyan, llvm-commits Differential Revision: https://reviews.llvm.org/D47422 llvm-svn: 333748
2018-06-01 21:21:33 +08:00
Changes to the DAG infrastructure
---------------------------------
Get rid of SETCCE Summary: It has been deprecated in favor of SETCCCARRY for a year now and isn't used by any in tree backend. Reviewers: efriedma, craig.topper, dblaikie, bkramer Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D47685 llvm-svn: 333939
2018-06-05 02:36:22 +08:00
[docs] Add the release notes about Debug Entry Values Note that x86, arm and aarch64 targets support the Debug Entry Values feature by default. Differential Revision: https://reviews.llvm.org/D77494
2020-04-07 18:05:22 +08:00
Changes to the Debug Info
---------------------------------
Bump the trunk major version to 12 and clear the release notes.
2020-07-15 17:40:53 +08:00
During this release ...
[docs] Add the release notes about Debug Entry Values Note that x86, arm and aarch64 targets support the Debug Entry Values feature by default. Differential Revision: https://reviews.llvm.org/D77494
2020-04-07 18:05:22 +08:00
[docs][llvm-dwarfdump] Add the release notes about --show-section-sizes Note that the llvm-dwarfdump has the new option. Differential Revision: https://reviews.llvm.org/D77495
2020-04-10 16:33:33 +08:00
Changes to the LLVM tools
---------------------------------
[LLVM][llvm-cov] Inclusive language: rename option -name-whitelist to -name-allowlist Renamed the option for llvm-cov and changed variable names to use more inclusive terms. Also changed the binary for the test. Reviewed By: alanphipps Differential Revision: https://reviews.llvm.org/D112816
2021-11-26 20:02:21 +08:00
* llvm-cov: `-name-allowlist` is now accepted in addition to `-name-whitelist`.
`-name-whitelist` is marked as deprecated and to be removed in future
releases.
[docs] Update release notes to mention lli JIT engine switch
2021-07-26 05:58:43 +08:00
Add LLDB section to the release notes llvm-svn: 365228
2019-07-06 01:58:30 +08:00
Changes to LLDB
[docs][lldb] Fix lldb item in releasenotes Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D83962
2020-07-17 01:07:12 +08:00
---------------------------------
Add LLDB section to the release notes llvm-svn: 365228
2019-07-06 01:58:30 +08:00
Add release notes for the LLDB impact from the array type name change Changing the array type printing from `int [N]` to `int[N]` impacts lldb pretty printer registration & may need to be updated to handle the dropped space between type and dimensions.
2021-10-26 01:17:44 +08:00
* A change in Clang's type printing has changed the way LLDB names array types
(from ``int [N]`` to ``int[N]``) - LLDB pretty printer type name matching
code may need to be updated to handle this.
[lldb] Update release notes with non-address bit handling changes This adds the "memory find" (https://reviews.llvm.org/D117299) and "memory tag" (https://reviews.llvm.org/D117672) commands and puts them all in one list.
2022-01-24 19:16:34 +08:00
* The following commands now ignore non-address bits (e.g. AArch64 pointer
signatures) in address arguments. In addition, non-address bits will not
be shown in the output of the commands.
* ``memory find``
* ``memory read``
* ``memory tag read``
* ``memory tag write``
Add release notes for the LLDB impact from the array type name change Changing the array type printing from `int [N]` to `int[N]` impacts lldb pretty printer registration & may need to be updated to handle the dropped space between type and dimensions.
2021-10-26 01:17:44 +08:00
[lldb] Add option to show memory tags in memory read output This adds an option --show-tags to "memory read". (lldb) memory read mte_buf mte_buf+32 -f "x" -s8 --show-tags 0x900fffff7ff8000: 0x0000000000000000 0x0000000000000000 (tag: 0x0) 0x900fffff7ff8010: 0x0000000000000000 0x0000000000000000 (tag: 0x1) Tags are printed on the end of each line, if that line has any tags associated with it. Meaning that untagged memory output is unchanged. Tags are printed based on the granule(s) of memory that a line covers. So you may have lines with 1 tag, with many tags, no tags or partially tagged lines. In the case of partially tagged lines, untagged granules will show "<no tag>" so that the ordering is obvious. For example, a line that covers 2 granules where the first is not tagged: (lldb) memory read mte_buf-16 mte_buf+16 -l32 -f"x" --show-tags 0x900fffff7ff7ff0: 0x00000000 <...> (tags: <no tag> 0x0) Untagged lines will just not have the "(tags: ..." at all. Though they may be part of a larger output that does have some tagged lines. To do this I've extended DumpDataExtractor to also print memory tags where it has a valid execution context and is asked to print them. There are no special alignment requirements, simply use "memory read" as usual. All alignment is handled in DumpDataExtractor. We use MakeTaggedRanges to find all the tagged memory in the current dump, then read all that into a MemoryTagMap. The tag map is populated once in DumpDataExtractor and re-used for each subsequently printed line (or recursive call of DumpDataExtractor, which some formats do). Reviewed By: omjavaid Differential Revision: https://reviews.llvm.org/D107140
2021-10-29 23:11:14 +08:00
* The ``memory read`` command has a new option ``--show-tags``. Use this option
to show memory tags beside the contents of tagged memory ranges.
Add an unsigned shift base sanitizer It's not undefined behavior for an unsigned left shift to overflow (i.e. to shift bits out), but it has been the source of bugs and exploits in certain codebases in the past. As we do in other parts of UBSan, this patch adds a dynamic checker which acts beyond UBSan and checks other sources of errors. The option is enabled as part of -fsanitize=integer. The flag is named: -fsanitize=unsigned-shift-base This matches shift-base and shift-exponent flags. <rdar://problem/46129047> Differential Revision: https://reviews.llvm.org/D86000
2020-08-15 05:05:57 +08:00
Changes to Sanitizers
---------------------
Bump the trunk major version to 14 and clear the release notes.
2021-07-28 12:51:07 +08:00
External Open Source Projects Using LLVM 14
Bump the trunk version to 10.0.0svn and clear the release notes. llvm-svn: 366427
2019-07-18 19:51:05 +08:00
===========================================
Update release notes wrt OCaml bindings. llvm-svn: 225779
2015-01-13 17:48:02 +08:00
Trunk release notes now refer to 4.0.0 llvm-svn: 275842
2016-07-19 02:02:23 +08:00
* A project...
Add external project LDC to release notes. LDC, the LLVM-based D compiler, is already using LLVM 3.4. llvm-svn: 194665
2013-11-14 13:57:40 +08:00
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
Additional Information
======================
A wide variety of additional information is available on the `LLVM web page
ReleaseNotes: update links to use https llvm-svn: 341785
2018-09-10 16:50:31 +08:00
<https://llvm.org/>`_, in particular in the `documentation
<https://llvm.org/docs/>`_ section. The web page also contains versions of the
Bump the trunk major version to 11 and clear the release notes.
2020-01-15 17:02:56 +08:00
API documentation which is up-to-date with the Git version of the source
Documentation: convert ReleaseNotes.html to reST. Patch by Anthony Mykhailenko with small fixes by me. llvm-svn: 169714
2012-12-10 07:14:26 +08:00
code. You can access versions of these documents specific to this release by
going into the ``llvm/docs/`` directory in the LLVM tree.
If you have any questions or comments about LLVM, please feel free to contact
ReleaseNotes: update links to use https llvm-svn: 341785
2018-09-10 16:50:31 +08:00
us via the `mailing lists <https://llvm.org/docs/#mailing-lists>`_.