Improve instcombine's handling of integer min and max in two ways:
authorDan Gohman <gohman@apple.com>
Tue, 16 Sep 2008 18:46:06 +0000 (18:46 +0000)
committerDan Gohman <gohman@apple.com>
Tue, 16 Sep 2008 18:46:06 +0000 (18:46 +0000)
commit81b28ceab6bd0ed6a784b7dc952ddb0b03fc6de7
tree057a8a72e899e9640c6b3892016da39c468f4fa6
parent19a341acb8df340651053c1ebb2403232103445b
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
lib/Analysis/ScalarEvolution.cpp
lib/Transforms/Scalar/InstructionCombining.cpp
test/Transforms/InstCombine/adjust-for-sminmax.ll [new file with mode: 0644]
test/Transforms/InstCombine/preserve-sminmax.ll [new file with mode: 0644]