[all-commits] [llvm/llvm-project] 59521a: [InstCombine] update datalayout in test file; NFC

[RotateRight via All-commits]

  Branch: refs/heads/release/11.x
  Home:   https://github.com/llvm/llvm-project
  Commit: 59521a06026e3912319db118340d48430838db09
      https://github.com/llvm/llvm-project/commit/59521a06026e3912319db118340d48430838db09
  Author: Sanjay Patel <spatel at rotateright.com>
  Date:   2020-07-16 (Thu, 16 Jul 2020)

  Changed paths:
    M llvm/test/Transforms/InstCombine/or.ll

  Log Message:
  -----------
  [InstCombine] update datalayout in test file; NFC

We need to specify legal integer widths to trigger PR46712,
so add those here. This doesn't appear to affect any existing
tests, and it's not clear why a datalayout would not include
any legal integer widths.

While here, change some variable names that include 'tmp' to
avoid warnings from the auto-generating script for CHECK lines.

(cherry picked from commit efc30e591bb5a6e869fd8e084bd310ae516b0fae)


  Commit: 12aa43e621ff3b60b515eaf33bb25ba439094140
      https://github.com/llvm/llvm-project/commit/12aa43e621ff3b60b515eaf33bb25ba439094140
  Author: Sanjay Patel <spatel at rotateright.com>
  Date:   2020-07-16 (Thu, 16 Jul 2020)

  Changed paths:
    M llvm/lib/Transforms/InstCombine/InstCombineAndOrXor.cpp
    M llvm/test/Transforms/InstCombine/or.ll

  Log Message:
  -----------
  [InstCombine] prevent infinite looping in or-icmp fold (PR46712)

I'm not sure if the test is truly minimal, but we need to
induce a situation where a value becomes a constant but is
not immediately folded before getting to the 'or' transform.

(cherry picked from commit d8b268680d0858aaf30cb1a278b64b11361bc780)


Compare: https://github.com/llvm/llvm-project/compare/73e8ca7bbad5...12aa43e621ff