| commit | 738533c84aeb56fff94b19c71714f54ae91c3670 | [log] [tgz] |
|---|---|---|
| author | Sander de Smalen <sander.desmalen@arm.com> | Mon Jun 24 11:06:16 2024 +0100 |
| committer | GitHub <noreply@github.com> | Mon Jun 24 11:06:16 2024 +0100 |
| tree | 43c04f7eb70d28519316ea52a339a8d7822afb1a | |
| parent | dfbfb6c5c6dba8a25c7a9769e969d56ba19fc14d [diff] |
[AArch64] Consider streaming mode in TTI interfaces for vectorization. (#96305) At the moment, vectorization is only enabled in streaming(-compatible) mode when enabled through an option. But the interfaces should check more than just 'hasSVE()', because a function with +sme in streaming mode should also vectorize with the option enabled. Additionally, a streaming-compatible function should only be able to use fixed-length autovec if SVE is available, otherwise the vector code will be scalarised by the backend.
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.