llvm-project.git/llvm/test/Transforms/SLPVectorizer/ARM, branch users/nico/python-2 Unnamed repository; edit this file 'description' to name the repository. [SLP]Check the MainOp matches the requirements for the instructions 2025-01-28T14:00:52+00:00 Alexey Bataev a.bataev@outlook.com 2025-01-28T13:57:10+00:00 a1ab5b4c87256ce7e99d6fd4bd0c62641e6ce853 Need to include MainOp into the analysis of the instructions in getSameOpcode to be sure that it is checked for the requirements to prevent crashes during further analysis. 
Need to include MainOp into the analysis of the instructions in
getSameOpcode to be sure that it is checked for the requirements to
prevent crashes during further analysis.
[SLP]Fix PR106909: add a check for unsafe FP operations. 2024-09-01T14:10:09+00:00 Alexey Bataev a.bataev@outlook.com 2024-09-01T14:10:09+00:00 6e68fa921bb7bf5ceb0b5036bb7d71399d5c7906 NEON has non-IEEE compliant denormal flushing and the compiler should check if it safe to vectorize instructions for NEON in non-fast math mode. Fixes https://github.com/llvm/llvm-project/issues/106909 
NEON has non-IEEE compliant denormal flushing and the compiler should
check if it safe to vectorize instructions for NEON in non-fast math
mode.

Fixes https://github.com/llvm/llvm-project/issues/106909
[SLP][NFC]Add a test with unsafe fp vectorization. 2024-09-01T14:05:36+00:00 Alexey Bataev a.bataev@outlook.com 2024-09-01T14:05:07+00:00 803ab280901588bdb92c52f8ea241caaa3926d8f 






[SLP][NFC]Add insertsubvector test with small source vector, NFC.
2023-10-05T13:03:58+00:00

Alexey Bataev
a.bataev@outlook.com

2023-10-05T12:59:10+00:00

2c49311dead19a274a3ce2d422c75264ecd160d2












[NFC][Py Reformat] Reformat lit.local.cfg python files in llvm
2023-05-17T15:03:15+00:00

Tobias Hieta
tobias@hieta.se

2023-05-17T09:01:54+00:00

f84bac329ba6c9f0c022bcf77237e912362e247a

This is a follow-up to b71edfaa4ec3c998aadb35255ce2f60bba2940b0
since I forgot the lit.local.cfg files in that one.

Reformatting is done with `black`.

If you end up having problems merging this commit because you
have made changes to a python file, the best way to handle that
is to run git checkout --ours <yourfile> and then reformat it
with black.

If you run into any problems, post to discourse about it and
we will try to help.

RFC Thread below:

https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Reviewed By: barannikov88, kwk

Differential Revision: https://reviews.llvm.org/D150762





This is a follow-up to b71edfaa4ec3c998aadb35255ce2f60bba2940b0
since I forgot the lit.local.cfg files in that one.

Reformatting is done with `black`.

If you end up having problems merging this commit because you
have made changes to a python file, the best way to handle that
is to run git checkout --ours <yourfile> and then reformat it
with black.

If you run into any problems, post to discourse about it and
we will try to help.

RFC Thread below:

https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Reviewed By: barannikov88, kwk

Differential Revision: https://reviews.llvm.org/D150762







[SLPVectorizer] Convert some tests to opaque pointers (NFC)
2023-01-04T15:34:39+00:00

Nikita Popov
npopov@redhat.com

2023-01-04T15:32:48+00:00

a34ae06c209752cdb3756cad89e0ea227fffd4d4












[SLP] Convert some tests to opaque pointers (NFC)
2022-12-23T09:02:57+00:00

Nikita Popov
npopov@redhat.com

2022-12-23T09:01:56+00:00

580210a0c938531ef9fd79f9ffedb93eeb2e66c2












[test][SLPVectorizer] Use -passes syntax in RUN lines. NFC
2022-10-13T08:44:38+00:00

Bjorn Pettersson
bjorn.a.pettersson@ericsson.com

2022-10-12T17:59:50+00:00

3be72f402925b99adbec4a2ee5bacdf76ba6c8d1












[opt] Don't translate legacy -analysis flag to require<analysis>
2022-10-07T21:54:34+00:00

Arthur Eubanks
aeubanks@google.com

2022-10-07T20:12:59+00:00

f3a928e2334a4e8e3f09406f2ce7e1cbac520f95

Tests relying on this should explicitly use -passes='require<analysis>,foo'.





Tests relying on this should explicitly use -passes='require<analysis>,foo'.







[SLP] Add insertelement instructions to vectorizable tree
2021-05-13T04:41:45+00:00

Anton Afanasyev
anton.a.afanasyev@gmail.com

2021-03-16T07:23:13+00:00

ab2c499d3a2ed3d3e13d96e456c57fb35a114b31

Add new type of tree node for `InsertElementInst` chain forming vector.
These instructions could be either removed, or replaced by shuffles during
vectorization and we can add this node to cost model, so naturally estimating
their cost, getting rid of `CompensateCost` tricks and reducing further work
for InstCombine. This fixes PR40522 and PR35732 in a natural way. Also this
patch is the first step towards revectorization of partially vectorization
(to fix PR42022 completely). After adding inserts to tree the next step is
to add vector instructions there (for instance, to merge `store <2 x float>`
and `store <2 x float>` to `store <4 x float>`).

Fixes PR40522 and PR35732.

Differential Revision: https://reviews.llvm.org/D98714





Add new type of tree node for `InsertElementInst` chain forming vector.
These instructions could be either removed, or replaced by shuffles during
vectorization and we can add this node to cost model, so naturally estimating
their cost, getting rid of `CompensateCost` tricks and reducing further work
for InstCombine. This fixes PR40522 and PR35732 in a natural way. Also this
patch is the first step towards revectorization of partially vectorization
(to fix PR42022 completely). After adding inserts to tree the next step is
to add vector instructions there (for instance, to merge `store <2 x float>`
and `store <2 x float>` to `store <4 x float>`).

Fixes PR40522 and PR35732.

Differential Revision: https://reviews.llvm.org/D98714