| commit | bd6eb54886ad12fb523e924e7291abfa2b010e3c | [log] [tgz] |
|---|---|---|
| author | Paul Walker <paul.walker@arm.com> | Fri Mar 08 12:09:05 2024 +0000 |
| committer | GitHub <noreply@github.com> | Fri Mar 08 12:09:05 2024 +0000 |
| tree | 854ea76359d2f50aa541a02d6c64e0afadeca478 | |
| parent | 4d478bcb4fc4fcf6532b725a0d070cb0c0cf9430 [diff] |
[LLVM][CodeGen] Teach SelectionDAG how to expand FREM to a vector math call. (#83859) This removes, at least when a vector library is available, a failure case for scalable vectors. Doing so means we can confidently cost vector FREM instructions without making an assumption that later passes will transform the IR before it gets to the code generator. NOTE: Whilst only FREM has been implemented the same mechanism can be used for the other libm related ISD nodes.
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.