Give each mlir::Block a stable ID within its parent region (#207617) Assign each mlir::Block a stable ID within its parent region, mirroring llvm::BasicBlock/llvm::Function (called ID, not number, since a block/op number denotes position in MLIR): Block gains getBlockID() and reads -1u while it has no parent region; Region gains nextBlockID with getMaxBlockID() and getBlockIDEpoch(); the block ilist traits assign the ID on add/transfer and invalidate it on removal; and GraphTraits<mlir::Block*>/<mlir::Region*> expose getNumber/getMaxNumber/getNumberEpoch. This makes GraphHasNodeNumbers<mlir::Block*> true, moving MLIR's CFGLoopInfo and dominator tree onto the number-indexed path. MLIR never renumbers blocks, so the epoch is a fixed 0. Prerequisite for requiring GraphHasNodeNumbers in llvm::LoopInfoBase and dropping its DenseMap fallback. Aided by Claude Opus 4.8
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.