[all-commits] [llvm/llvm-project] 28d9ae: [LoopIdiom] Use costing to determine CRC strategy ...

[Sean Clarke via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 28d9aec513c63beffd2631412adfae327763559e
      https://github.com/llvm/llvm-project/commit/28d9aec513c63beffd2631412adfae327763559e
  Author: Sean Clarke <sclarke at tenstorrent.com>
  Date:   2026-07-31 (Fri, 31 Jul 2026)

  Changed paths:
    M llvm/lib/Transforms/Scalar/LoopIdiomRecognize.cpp
    M llvm/test/Transforms/LoopIdiom/AArch64/cyclic-redundancy-check.ll
    M llvm/test/Transforms/LoopIdiom/RISCV/cyclic-redundancy-check.ll
    M llvm/test/Transforms/LoopIdiom/X86/cyclic-redundancy-check.ll
    A llvm/test/Transforms/LoopIdiom/crc-debugify-remarks.ll
    M llvm/test/Transforms/LoopIdiom/cyclic-redundancy-check.ll

  Log Message:
  -----------
  [LoopIdiom] Use costing to determine CRC strategy (#211040)

The CRC loop clmul optimization currently only runs under optsize,
despite being significantly faster than the Sarwate table optimization
in many cases. Model the costs of each approach and weigh them against
each other to determine which optimization should be used. Since the
benefits of clmul are unclear for optsize, simply bail in that case
instead.

Assisted-by: Claude Opus 4.8



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