| tag | 306ba32dba76f789701915e0339093957e48a671 | |
|---|---|---|
| tagger | Tobias Hieta <tobias@hieta.se> | Sat Jul 29 08:43:14 2023 +0200 |
| object | cff7a7747db02d1214b20e98677e5ddcb402ffe0 |
LLVM 17.0.0-rc1 Release
| commit | cff7a7747db02d1214b20e98677e5ddcb402ffe0 | [log] [tgz] |
|---|---|---|
| author | Nikita Popov <npopov@redhat.com> | Fri Jul 28 14:21:00 2023 +0200 |
| committer | Tobias Hieta <tobias@hieta.se> | Sat Jul 29 08:40:45 2023 +0200 |
| tree | b66bdabded8c2f50322588e21ca8f427dfc0b369 | |
| parent | bafedb1c2c64823ecee547f9776c4311a7f0930c [diff] |
[ThinLTO] Use module hash instead of module ID for cache key This is a followup to D151165. Instead of using the module ID, use the module hash for sorting the import list. The module hash is what will actually be included in the hash. This has the advantage of being independent of the module order, which is something that Rust relies on. A caveat here is that the test doesn't quite work for linkonce_odr functions, because the function may be imported from two different modules, and the first one on the llvm-lto2 command line gets picked (rather than, say, the prevailing copy). This doesn't really matter for Rust's purposes (because it does not use linkonce_odr linkage), but may still be worth addressing. For now I'm using a variant of the test using internal instead of linkonce_odr functions. Differential Revision: https://reviews.llvm.org/D156525 (cherry picked from commit 279c2971951c2ea58a2bd1e6687ce61451f9d329)
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, or #llvm IRC channel on OFTC.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.