[RISCV] Replace sexti32/zexti32 in isel patterns where only one part of their PatFrag...
authorCraig Topper <craig.topper@sifive.com>
Fri, 27 Nov 2020 19:11:41 +0000 (11:11 -0800)
committerCraig Topper <craig.topper@sifive.com>
Fri, 27 Nov 2020 19:37:25 +0000 (11:37 -0800)
commitf325b4bbceb5e680e64532dd018b3c0a36d1b01a
treeb5a9fb22094926822d42ec55e1a29592b0de7b7b
parentb7bde0e4f3d2ca9d2fb25f911ba7eb9d2a4cbd05
[RISCV] Replace sexti32/zexti32 in isel patterns where only one part of their PatFrags can match. NFCI

We had an zexti32 after a sign_extend_inreg. The AND X, 0xffffffff
part of the zexti32 should never occur since SimplifyDemandedBits
from the sign_extend_inreg would have removed it.

We also had sexti32 as the root node of a pattern, but SelectionDAGISel
matches assertsext early before the tablegen based patterns are
evaluated.
llvm/lib/Target/RISCV/RISCVInstrInfoD.td
llvm/lib/Target/RISCV/RISCVInstrInfoF.td