Folding into a sra(mul) / srl(mul) into a mulh introduces an extra multiplication to compute the high half of the multiplication,
while it is more profitable to compute the high and lower halfs with a single mul_lohi.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Time | Test | |
---|---|---|
60,040 ms | x64 debian > MLIR.Examples/standalone::test.toy |
Event Timeline
llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
9263 | Probably should use !hasOneUse instead of computing use_size | |
llvm/test/CodeGen/AMDGPU/mul_lohi.ll | ||
1 ↗ | (On Diff #459710) | Test name is too general for what this is testing |
3 ↗ | (On Diff #459710) | This isn't a kernel, rename function |
5–7 ↗ | (On Diff #459710) | Might as well generate these checks |
8–9 ↗ | (On Diff #459710) | Should use named values in test |
16 ↗ | (On Diff #459710) | Can you also add a case with a type with illegal mul_lohi, a vector case, and also a shift with a non-constant case, and an off by one shift amount? |
- Use !hasOneUse instead of use_size
- renamed test from mul_lohi.ll to dagcomb-mullohi.ll
- named the instructions in the test using the instnamer
- generated test assertions using update_llc_test_checks.py (I wasn't familiar with it, I'm glad to know it now :) )
- added test-cases for
- unsigned (already there)
- signed
- type for which mul_lohi is not legal
- vector type
- non-const shift
- shift to the right by one more than the limit (so a v_mul_hi is used)
- shift to the right by one less than the limit (so a v_mad is used)
Thanks for the review arsenm. I took into account the reviews in the update of the patch.
I'm not sure if there is a naming convention for the tests in this part: I renamed into dagcomb-mullohi.ll.
llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
9249 | @jmmartinez I'm getting static analysis warnings that this is always true - should this be: if (U->getOpcode() != ISD::SRL && U->getOpcode() != ISD::SRA) { |
llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
9249 | Well spotted! I'll submit a fix for it. BTW what are you using for static analysis? |
llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
9249 | Cheers - VisualAssist 'code inspection' caught this one |
llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp | ||
---|---|---|
9249 | Sorry, amazingly its Intellisense that caught it - they get listed in the same window |
@jmmartinez I'm getting static analysis warnings that this is always true - should this be: