[NFC][VPlan] Add initial tests for future VPlan-based stride MV I tried to include both the features that current LoopAccessAnalysis-based transformation supports (e.g., trunc/sext of stride) but also cases where the current implementation behaves poorly, e.g., https://godbolt.org/z/h31c3zKxK; as well as some other potentially interesting scenarios I could imagine. The are two test files with the same content. One is for VPlan dump change of the future transformation alone (I'll update `-vplan-print-after` in the next PR), another is for the full vectorizer pipeline. The latter have two `RUN:` lines: * No multiversioning, so the next PR diff can show the transformation itself * Stride multiversionin performed in LAA, so that we can compare future VPlan-based transformation vs old behavior.
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.