diff options
author | Dan Gohman <gohman@apple.com> | 2008-09-16 18:46:06 +0000 |
---|---|---|
committer | Dan Gohman <gohman@apple.com> | 2008-09-16 18:46:06 +0000 |
commit | 81b28ceab6bd0ed6a784b7dc952ddb0b03fc6de7 (patch) | |
tree | 057a8a72e899e9640c6b3892016da39c468f4fa6 /test/Analysis/ScalarEvolution/2008-02-11-ReversedCondition.ll | |
parent | 19a341acb8df340651053c1ebb2403232103445b (diff) | |
download | external_llvm-81b28ceab6bd0ed6a784b7dc952ddb0b03fc6de7.zip external_llvm-81b28ceab6bd0ed6a784b7dc952ddb0b03fc6de7.tar.gz external_llvm-81b28ceab6bd0ed6a784b7dc952ddb0b03fc6de7.tar.bz2 |
Improve instcombine's handling of integer min and max in two ways:
- Recognize expressions like "x > -1 ? x : 0" as min/max and turn them
into expressions like "x < 0 ? 0 : x", which is easily recognizable
as a min/max operation.
- Refrain from folding expression like "y/2 < 1" to "y < 2" when the
comparison is being used as part of a min or max idiom, like
"y/2 < 1 ? 1 : y/2". In that case, the division has another use, so
folding doesn't eliminate it, and obfuscates the min/max, making it
harder to recognize as a min/max operation.
These benefit ScalarEvolution, CodeGen, and anything else that wants to
recognize integer min and max.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@56246 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/Analysis/ScalarEvolution/2008-02-11-ReversedCondition.ll')
0 files changed, 0 insertions, 0 deletions