LLVM 18.0.0git Release Notes


These are in-progress notes for the upcoming LLVM 18 release. Release notes for previous releases can be found on the Download Page.


This document contains the release notes for the LLVM Compiler Infrastructure, release 18.0.0git. Here we describe the status of LLVM, including major improvements 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 from the LLVM releases web site.

For more information about LLVM, including information about the latest release, please check out the main LLVM web site. If you have questions or comments, the Discourse forums is a good place to ask them.

Note that if you are reading this file from a Git checkout or the main 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 page.

Non-comprehensive list of changes in this release

Update on required toolchains to build LLVM

Changes to the LLVM IR

  • The llvm.stacksave and llvm.stackrestore intrinsics now use an overloaded pointer type to support non-0 address spaces.

  • The constant expression variants of the following instructions have been removed:

    • and

    • or

  • Added llvm.exp10 intrinsic.

Changes to LLVM infrastructure

Changes to building LLVM

Changes to TableGen

Changes to Interprocedural Optimizations

Changes to the AArch64 Backend

Changes to the AMDGPU Backend

  • llvm.sqrt.f32 is now lowered correctly. Use llvm.amdgcn.sqrt.f32 for raw instruction access.

  • Implemented llvm.stacksave and llvm.stackrestore intrinsics.

  • Implemented llvm.get.rounding

Changes to the ARM Backend

Changes to the AVR Backend

Changes to the DirectX Backend

Changes to the Hexagon Backend

Changes to the LoongArch Backend

Changes to the MIPS Backend

Changes to the PowerPC Backend

Changes to the RISC-V Backend

  • Zihintntl extension version was upgraded to 1.0 and is no longer experimental.

Changes to the WebAssembly Backend

Changes to the Windows Target

Changes to the X86 Backend

Changes to the OCaml bindings

Changes to the Python bindings

  • The python bindings have been removed.

Changes to the C API

  • Added LLVMGetTailCallKind and LLVMSetTailCallKind to allow getting and setting tail, musttail, and notail attributes on call instructions.

  • The following functions for creating constant expressions have been removed, because the underlying constant expressions are no longer supported. Instead, an instruction should be created using the LLVMBuildXYZ APIs, which will constant fold the operands if possible and create an instruction otherwise:

    • LLVMConstAnd

    • LLVMConstOr

Changes to the CodeGen infrastructure

  • PrologEpilogInserter no longer supports register scavenging during forwards frame index elimination. Targets should use backwards frame index elimination instead.

  • RegScavenger no longer supports forwards register scavenging. Clients should use backwards register scavenging instead, which is preferred because it does not depend on accurate kill flags.

Changes to the Metadata Info

Changes to the Debug Info

Changes to the LLVM tools

  • llvm-symbolizer now treats invalid input as an address for which source information is not found.

  • llvm-readelf now supports --extra-sym-info (-X) to display extra information (section name) when showing symbols.

  • llvm-nm now supports the --line-numbers (-l) option to use debugging information to print symbols’ filenames and line numbers.

Changes to LLDB

  • Methods in SBHostOS related to threads have had their implementations removed. These methods will return a value indicating failure.

Changes to Sanitizers

  • HWASan now defaults to detecting use-after-scope bugs.

Other Changes

  • The Flags field of llvm::opt::Option has been split into Flags and Visibility to simplify option sharing between various drivers (such as clang, clang-cl, or flang) that rely on Clang’s Options.td. Overloads of llvm::opt::OptTable that use FlagsToInclude have been deprecated. There is a script and instructions on how to resolve conflicts - see https://reviews.llvm.org/D157150 and https://reviews.llvm.org/D157151 for details.

  • On Linux, FreeBSD, and NetBSD, setting the environment variable LLVM_ENABLE_SYMBOLIZER_MARKUP causes tools to print stacktraces using Symbolizer Markup. This works even if the tools have no embedded symbol information (i.e. are fully stripped); llvm-symbolizer can symbolize the markup afterwards using debuginfod.

External Open Source Projects Using LLVM 15

  • A project…

Additional Information

A wide variety of additional information is available on the LLVM web page, in particular in the documentation section. The web page also contains versions of the API documentation which is up-to-date with the Git version of the source 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 us via the Discourse forums.