projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 300870a) | patch
[LoopVectorize][X86] Add operands to make it more obvious what line the CHECK concerns
authorSimon Pilgrim <llvm-dev@redking.me.uk>
Wed, 22 Sep 2021 09:08:14 +0000 (10:08 +0100)
committerSimon Pilgrim <llvm-dev@redking.me.uk>
Wed, 22 Sep 2021 09:08:32 +0000 (10:08 +0100)
commit41492d77ba65338b9eb2b7f401e47acf22e4ea19
treeedc32ce2dad2d87c52533e148eb13e6a6cc691e2tree | snapshot
parent300870a95c22fde840862cf57d82adba3e5bd633commit | diff
[LoopVectorize][X86] Add operands to make it more obvious what line the CHECK concerns

As we're checking the cost debug analysis these should match the original IR line - so we shouldn't have any variable naming issues.

I'm investigating v4i32 mul -> PMADDDW costs handling (for PR47437) and these CHECK lines were proving tricky to keep track of
llvm/test/Transforms/LoopVectorize/X86/mul_slm_16bit.ll diff | blob | history
Domain: System / Toolchain;