| commit | 21f04b1458c52ba875a23b58b02cf6b1f8db0661 | [log] [tgz] |
|---|---|---|
| author | Adam Paszke <adam.paszke@gmail.com> | Sat Jan 25 16:28:21 2025 +0100 |
| committer | GitHub <noreply@github.com> | Sat Jan 25 07:28:21 2025 -0800 |
| tree | e22f411541fcb0d7356f6cee80e017c4a4605256 | |
| parent | 9325a61aa0960595c22867799ebd157c8160fd86 [diff] |
Hold a queue of iterator ranges (not operations) in wouldOpBeTriviallyDead (#123642) Ranges let us push the whole blocks onto the queue in constant time. If one of the first ops in the block is side-effecting we'll be able to provide the answer quickly. The previous implementation had to walk the block and queue all the operations only to start traversing them again, which was a considerable slowdown for compile times of large MLIR programs in our benchmarks. --------- Co-authored-by: Jacques Pienaar <jpienaar@google.com>
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, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.