projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0a5d435) | patch
[SLP] Adjust debug output for store vectorization failure
authorPhilip Reames <preames@rivosinc.com>
Fri, 23 Sep 2022 16:56:08 +0000 (09:56 -0700)
committerPhilip Reames <listmail@philipreames.com>
Fri, 23 Sep 2022 16:58:15 +0000 (09:58 -0700)
commit954c1ed009d423ca9593ee63479a9394a23864fd
tree143d6ac28203cd966cbacc0a786b974d97afa859tree | snapshot
parent0a5d4355c961d04697154b02b74e7c3ff1f478c7commit | diff
[SLP] Adjust debug output for store vectorization failure

When store vectorization is infeasible, it's helpful to have a debug logging indication of why.  A case I've hit a couple times now is accidentally using -march instead of -mtriple and getting the default TTI results.  This causes max-vf to become 1, and thus hits the added logging line.
llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp diff | blob | history
Domain: System / Toolchain;