| commit | cca44e030ddd74c365fdd6b82946e61efa41dee2 | [log] [tgz] |
|---|---|---|
| author | Craig Topper <craig.topper@sifive.com> | Wed Jun 25 21:28:34 2025 -0700 |
| committer | GitHub <noreply@github.com> | Wed Jun 25 21:28:34 2025 -0700 |
| tree | bc3bb1ab0d811731bf4ad842d4ab98b6b338c686 | |
| parent | 5b5e95ceb8d68f709a3c6fee5cf8c09d74c32d51 [diff] |
[RISCV] Explicitly check for supported opcodes in optimizeCondBranch. NFC (#145622) We don't support any of the immediate branches in this function yet so explicitly exclude them rather than relying on isReg to return false. Remove use of AnalyzeBranch. It doesn't help us much. Part of the code was already getting the operands directly and it just complicated creating a new branch. I also inlined the modifyBranch function so we could use addReg on BuildMI.
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.