diff options
| author | Nicolai Hähnle <nicolai.haehnle@amd.com> | 2022-04-12 20:37:44 -0500 |
|---|---|---|
| committer | Nicolai Hähnle <nicolai.haehnle@amd.com> | 2022-05-02 17:40:03 -0500 |
| commit | deaa678137e52f51ca694fdfd1dc9988360fb69b (patch) | |
| tree | c46614c6329d0b139208002cad5cf107a9813c75 /llvm/lib/Object/Binary.cpp | |
| parent | 4f5d525b1d863183ca5a0dedf911a763330b91a4 (diff) | |
| download | llvm-deaa678137e52f51ca694fdfd1dc9988360fb69b.zip llvm-deaa678137e52f51ca694fdfd1dc9988360fb69b.tar.gz llvm-deaa678137e52f51ca694fdfd1dc9988360fb69b.tar.bz2 | |
AMDGPU/SDAG: Factor out the fold (add (mul x, y), y) --> mad_[iu]64_[iu]32
Refactor to simplify a follow-up change.
No functional change intended. However, there is a rather subtle logic
change: the subsequent combines (e.g. reassociation) are skipped *always*
when one of the operands of the add is a mul, instead of only when
additionally mad64_32 etc. are available. This change makes sense because
the subsequent combines should never apply when one of the operands is a
mul.
Differential Revision: https://reviews.llvm.org/D123833
Diffstat (limited to 'llvm/lib/Object/Binary.cpp')
0 files changed, 0 insertions, 0 deletions