| commit | 85fd83ed49604d1046e937afa76f3ad802e28822 | [log] [tgz] |
|---|---|---|
| author | Asher Mancinelli <ashermancinelli@gmail.com> | Fri Apr 04 06:13:30 2025 -0700 |
| committer | GitHub <noreply@github.com> | Fri Apr 04 06:13:30 2025 -0700 |
| tree | ad6535a2d213a509d548812894b39f8c7c26b141 | |
| parent | d2bcc11067e682a0753c1068e378d66d59edff73 [diff] |
[flang][nfc] Use llvm memmove intrinsic over regular call (#134294) Follow up to #134170. We should be using the LLVM intrinsics instead of plain fir.calls when we can. Existing code creates a declaration for the llvm intrinsic and a regular fir.call, which makes it hard for consumers of the IR to find all the intrinsic calls.
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.