aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-objdump/llvm-objdump.cpp
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2022-10-04 10:42:59 -0400
committerSanjay Patel <spatel@rotateright.com>2022-10-04 11:20:01 -0400
commit0a1210e482c7d8bd8d4bf1740a5175b29d05da17 (patch)
treed9f81223651e92cd92ca7ac067843592f0cde7bc /llvm/tools/llvm-objdump/llvm-objdump.cpp
parentab9a81f736acfb927b0e0b4f0de8710fc2379f70 (diff)
downloadllvm-0a1210e482c7d8bd8d4bf1740a5175b29d05da17.zip
llvm-0a1210e482c7d8bd8d4bf1740a5175b29d05da17.tar.gz
llvm-0a1210e482c7d8bd8d4bf1740a5175b29d05da17.tar.bz2
[InstSimplify] try harder to fold fmul with 0.0 operand
https://alive2.llvm.org/ce/z/oShzr3 This was noted as a missing fold in D134876 (with additional examples based on issue #58046). I'm assuming that fmul with a zero operand is rare enough that the use of ValueTracking will not noticeably increase compile-time. This adjusts a PowerPC codegen test that was added with D88388 because it would get folded away and no longer provide coverage for the bug fix.
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions