| commit | 0b6e04005ca0eab7c5566950d8595379a9f72d41 | [log] [tgz] |
|---|---|---|
| author | Craig Topper <craig.topper@sifive.com> | Mon Feb 12 09:17:50 2024 -0800 |
| committer | GitHub <noreply@github.com> | Mon Feb 12 09:17:50 2024 -0800 |
| tree | 15cb950c6819692808377f1689a816e46bb15af6 | |
| parent | 44d85c5b15bbf6226f442126735b764d81cbf6e3 [diff] |
[RISCV] Exclude X1 and X5 from register scavenging for long branch. (#80215) When a branch target is too far away we need to emit an indirect branch. We scavenge a register for this since we don't know we need this until after register allocation. Jumps using X1 and X5 as the source are hints to the hardware to pop the return-address stack. We should avoiding using them for jumps that aren't a return or tail call.
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.