This continues the refactoring work of selecting offset + address operands with the AddrOpsN pattern, previously called LoadOpsN.
This is not an NFC, since constant addresses are now folded into the offset in more places for v128.storeN_lane.
Paths
| Differential D139950
[WebAssembly] Use ComplexPattern on remaining memory instructions ClosedPublic Authored by luke on Dec 13 2022, 9:40 AM.
Details Summary This continues the refactoring work of selecting offset + address operands with the AddrOpsN pattern, previously called LoadOpsN. This is not an NFC, since constant addresses are now folded into the offset in more places for v128.storeN_lane.
Diff Detail
Event Timelineluke added a parent revision: D139631: [WebAssembly][NFC] Add ComplexPattern for loads.Dec 13 2022, 9:40 AM Comment Actions Nice!
luke retitled this revision from [WebAssembly] Use ComplexPattern on store address operands to [WebAssembly] Use ComplexPattern on remaining memory instructions.Dec 14 2022, 2:57 AM This revision is now accepted and ready to land.Dec 14 2022, 12:07 PM This revision was landed with ongoing or failed builds.Dec 15 2022, 2:21 AM Closed by commit rG0cd9c5176639: [WebAssembly] Use ComplexPattern on remaining memory instructions (authored by luke, committed by asb). · Explain Why This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 483101 llvm/lib/Target/WebAssembly/WebAssemblyISelDAGToDAG.cpp
llvm/lib/Target/WebAssembly/WebAssemblyInstrAtomics.td
llvm/lib/Target/WebAssembly/WebAssemblyInstrMemory.td
llvm/lib/Target/WebAssembly/WebAssemblyInstrSIMD.td
llvm/test/CodeGen/WebAssembly/simd-load-lane-offset.ll
llvm/test/CodeGen/WebAssembly/simd-offset.ll
|
It looks we don't convert atomic stores in this CL.. Is that going to be a follow-up, or is that not included in the plan? Is converting them different from the normal stores?