| commit | 8d71a2a905508f32ed201920ef7ac15a3ad8e4e6 | [log] [tgz] |
|---|---|---|
| author | Florian Hahn <flo@fhahn.com> | Sun Apr 06 09:48:52 2025 +0100 |
| committer | Florian Hahn <flo@fhahn.com> | Sun Apr 06 09:48:52 2025 +0100 |
| tree | 2dff79f60748740d80b14dab92faf841a26a8b59 | |
| parent | 53e1c8b118792b0177bff69d806c9e00034ceb1c [diff] |
[VPlan] Use ExitBocks to check in VPlan::isExitBlock (NFC). Exit blocks of the VPlan are now hold in ExitBlocks. Use it to check if a block is an exit block. Otherwise we currently mis-classify the scalar loop header also as exit block, as it is not explicitly connected to the exit blocks. NFC at the moment, as the helper currently is never queried with the scalar header, but that will change in the future.
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.