[all-commits] [llvm/llvm-project] 958cec: [LV] Remove use of llc from vectoriser tests (#154...

[David Sherwood via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 958cec0ab1bbbdc47ea207460de72c5fee24be70
      https://github.com/llvm/llvm-project/commit/958cec0ab1bbbdc47ea207460de72c5fee24be70
  Author: David Sherwood <david.sherwood at arm.com>
  Date:   2025-08-26 (Tue, 26 Aug 2025)

  Changed paths:
    A llvm/test/CodeGen/X86/vectorization-remarks-loopid-dbg.ll
    M llvm/test/Transforms/LoopVectorize/X86/avx512.ll
    M llvm/test/Transforms/LoopVectorize/X86/fp32_to_uint32-cost-model.ll
    M llvm/test/Transforms/LoopVectorize/X86/fp64_to_uint32-cost-model.ll
    M llvm/test/Transforms/LoopVectorize/X86/vectorization-remarks-loopid-dbg.ll
    M llvm/test/Transforms/LoopVectorize/X86/vectorization-remarks.ll

  Log Message:
  -----------
  [LV] Remove use of llc from vectoriser tests (#154759)

There were 5 X86 loop vectoriser tests that were piping the output from
opt into llc. I think in the directory test/Transforms/LoopVectorize we
should only be testing the output from the loop vectoriser pass. Any
codegen tests should live in test/CodeGen/X86 instead.

avx512.ll: it looks like we were really just testing that we generate
the right vector length.
fp32_to_uint32-cost-model.ll/fp64_to_uint32-cost-model.ll: the tests
only seem to care that we're not scalarising the fptoui, so I've
modified the test to check for vector ops. I've assumed there are
already codegen tests for fptoui vector operations.
vectorization-remarks-loopid-dbg.ll: i've copied this test to
CodeGen/X86/vectorization-remarks-loopid-dbg.ll for the llc RUN line
variant
vectorization-remarks.ll: seems to test the same thing as
vectorization-remarks-loopid-dbg.ll



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications