| commit | f575b7f51c87e9da013ee77909f85f6a5fd2a41f | [log] [tgz] |
|---|---|---|
| author | Krzysztof Parzyszek <kparzysz@quicinc.com> | Thu May 18 18:58:59 2023 -0700 |
| committer | Krzysztof Parzyszek <kparzysz@quicinc.com> | Fri May 19 12:05:26 2023 -0700 |
| tree | 584a26de03442194ac6c00f48ca6cc860840113c | |
| parent | 3e6da8dd29b78689ebc4feaedcfcaa4f25e3f7ae [diff] |
[Hexagon] Clone dependencies instead of moving in HVC Loads can share dependencies, and moving them for each load separately can end up placing them in a wrong location. There was already a check for that, but it wasn't correct. Instead of trying to find the right location for all moved instructions at once, create clones for each individual load.
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, or #llvm IRC channel on OFTC.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.