Centralize prefetch target storage in MachineFunction. (#184194) ### Prefetch Symbol Resolution Based on this [suggestion](https://discourse.llvm.org/t/rfc-code-prefetch-insertion/88668/29?u=rlavaee), we must identify if a prefetch target is defined in the current module to avoid **undefined symbol errors**. Since this occurs during sequential **CodeGen**, we must rely on function names rather than IR Module APIs. **Key Changes:** * **`MachineFunction` Integration:** Added a `PrefetchTargets` field (with serialization) to track all targets associated with a function. * **Guaranteed Emission:** All prefetch targets are now emitted regardless of basic block or callsite index matches to ensure the symbol exists. * **Fallback Placement:** Targets with non-matching callsite indices are emitted at the end of the block to resolve the reference.
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.