diff options
author | Matthias Braun <matze@braunis.de> | 2016-03-09 18:47:11 +0000 |
---|---|---|
committer | Matthias Braun <matze@braunis.de> | 2016-03-09 18:47:11 +0000 |
commit | c31032d607c25d8bc53d59b68b797285f2736ea1 (patch) | |
tree | bb204ddd638c0789effdaa2b5e147bd51b525adb /clang/test/CodeGen/arm-neon-numeric-maxmin.c | |
parent | 0b5d5b881f7130e9e678d18dc97e593614b5ee3e (diff) | |
download | bcm5719-llvm-c31032d607c25d8bc53d59b68b797285f2736ea1.tar.gz bcm5719-llvm-c31032d607c25d8bc53d59b68b797285f2736ea1.zip |
InstCombine: Restrict computeKnownBits() on all Values to OptLevel > 2
As part of r251146 InstCombine was extended to call computeKnownBits on
every value in the function to determine whether it happens to be
constant. This increases typical compiletime by 1-3% (5% in irgen+opt
time) in my measurements. On the other hand this case did not trigger
once in the whole llvm-testsuite.
This patch introduces the notion of ExpensiveCombines which are only
enabled for OptLevel > 2. I removed the check in InstructionSimplify as
that is called from various places where the OptLevel is not known but
given the rarity of the situation I think a check in InstCombine is
enough.
Differential Revision: http://reviews.llvm.org/D16835
llvm-svn: 263047
Diffstat (limited to 'clang/test/CodeGen/arm-neon-numeric-maxmin.c')
0 files changed, 0 insertions, 0 deletions