This document contains the release notes for the LLVM Compiler Infrastructure, release 8.0.0. 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 LLVM Developerâs Mailing List is a good place to send them.
Minimum Required Compiler Version¶As discussed on the mailing list, building LLVM will soon require more recent toolchains as follows:
Clang 3.5 Apple Clang 6.0 GCC 5.1 Visual Studio 2017A new CMake check when configuring LLVM provides a soft-error if your toolchain will become unsupported soon. You can opt out of the soft-error by setting the LLVM_TEMPORARILY_ALLOW_OLD_TOOLCHAIN
CMake variable to ON
.
These are issues that couldnât be fixed before the release. See the bug reports for the latest status.
Non-comprehensive list of changes in this release¶add_llvm_loadable_module
CMake macro has been removed. The add_llvm_library
macro with the MODULE
argument now provides the same functionality. See Writing an LLVM Pass..reloc
directive.-x86-discriminate-memops
LLVM Flag.-x86-discriminate-memops
is run under the observation of the recommender. The recommender identifies certain memory access instructions by their binary file address, and recommends a prefetch of a specific type (NTA, T0, etc) be performed at a specified fixed offset from such an instructionâs memory operand. Next, this information needs to be converted to the AutoFDO syntax and the resulting profile may be passed back to the compiler with the LLVM flag -prefetch-hints-file
, together with the exact same set of compilation parameters used for the original binary. More information is available in the RFC.The ORC (On Request Compilation) JIT APIs have been updated to support concurrent compilation. The existing (non-concurrent) ORC layer classes and related APIs are deprecated, have been renamed with a âLegacyâ prefix (e.g. LegacyIRCompileLayer). The deprecated clasess will be removed in LLVM 9.
An example JIT stack using the concurrent ORC APIs, called LLJIT, has been added (see include/llvm/ExecutionEngine/Orc/LLJIT.h). The lli tool has been updated to use LLJIT.
MCJIT and ExecutionEngine continue to be supported, though ORC should be preferred for new projects.
Changes to the AArch64 Target¶.arch_extension
assembler directive, just like on ARM.R_MIPS_JALR
and R_MICROMIPS_JALR
relocations. These relocations provide hints to a linker for optimization of jumps to protected symbols.pll.ps
, plu.ps
, cvt.s.pu
, cvt.s.pl
, cvt.ps
, sigrie
).__float128
supportpack
/unpack
and stxvw4x.be
/stxvd2x.be
___fixunstfti
/floattitf
in compiler-rt to support conversion between IBM double-double and unsigned int128-mzvector
option now actually enables the __vector
and __bool
keywords, the vec_step
intrinsic now works, and the vec_insert_and_zero
and vec_orc
intrinsics now generate correct code.__float128
keyword, which had been accidentally enabled in some earlier releases, is now no longer supported. On SystemZ, the long double
data type itself already uses the IEEE 128-bit floating-point format.strcmp
or memcmp
, the generated code no longer returns INT_MIN
as the negative result value under any circumstances.llvm.avx512.
replaced with llvm.avx512.mask.
. The old intrinsics will be removed in a future release.cascadelake
as a CPU name for -march. This is skylake-avx512
with the addition of the avx512vnni
instruction set.The WebAssembly target is no longer âexperimentalâ! Itâs now built by default, rather than needing to be enabled with LLVM_EXPERIMENTAL_TARGETS_TO_BUILD.
The object file format and core C ABI are now considered stable. That said, the object file format has an ABI versioning capability, and one anticipated use for it will be to add support for returning small structs as multiple return values, once the underlying WebAssembly platform itself supports it. Additionally, multithreading support is not yet included in the stable ABI.
Changes to LLDB¶D is a language with C-like syntax and static typing. It pragmatically combines efficiency, control, and modeling power, with safety and programmer productivity. D supports powerful concepts like Compile-Time Function Execution (CTFE) and Template Meta-Programming, provides an innovative approach to concurrency and offers many classical paradigms.
LDC uses the frontend from the reference compiler combined with LLVM as backend to produce efficient native code. LDC targets x86/x86_64 systems like Linux, OS X, FreeBSD and Windows and also Linux on ARM and PowerPC (32/64 bit). Ports to other architectures like AArch64 and MIPS64 are underway.
Open Dylan Compiler¶Dylan is a multi-paradigm functional and object-oriented programming language. It is dynamic while providing a programming model designed to support efficient machine code generation, including fine-grained control over dynamic and static behavior. Dylan also features a powerful macro facility for expressive metaprogramming.
The Open Dylan compiler can use LLVM as one of its code-generating back-ends, including full support for debug info generation. (Open Dylan generates LLVM bitcode directly using a native Dylan IR and bitcode library.) Development of a Dylan debugger and interactive REPL making use of the LLDB libraries is in progress.
Zig Programming Language¶Zig is a system programming language intended to be an alternative to C. It provides high level features such as generics, compile time function execution, and partial evaluation, while exposing low level LLVM IR features such as aliases and intrinsics. Zig uses Clang to provide automatic import of .h symbols, including inline functions and simple macros. Zig uses LLD combined with lazily building compiler-rt to provide out-of-the-box cross-compiling for all supported targets.
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 Subversion 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 mailing lists.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3