| commit | 0b8528e127d898a8bdb0d96c9afc7f3baa4bc3f5 | [log] [tgz] |
|---|---|---|
| author | Philip Reames <[email protected]> | Tue May 06 20:19:53 2025 |
| committer | GitHub <[email protected]> | Tue May 06 20:19:53 2025 |
| tree | e4f4fb0622ee0b9e7df233148f6a3db9580e7c36 | |
| parent | 7087ee6bc79c95692c609cf174b3cb5e6e0c1820 [diff] |
[instcombine] Adjust style of MemIntrinsic code to be more idiomatic [nfc] (#138715) Use an existing helper function. Remove the use of a local Changed variable which doesn't seem to interact with surrounding transforms in any meaningful way. (Both memcpy and memmove are MemTransfer instructions, so switching from one to the other doesn't change results.) Posted for review mostly for a sanity check that I'm not missing something with the logic around the Change flag.
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.