projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 69683f1) | patch
Follow up to 260439, Speculative fix to clang builders
authorPhilip Reames <listmail@philipreames.com>
Wed, 10 Feb 2016 22:22:41 +0000 (22:22 +0000)
committerPhilip Reames <listmail@philipreames.com>
Wed, 10 Feb 2016 22:22:41 +0000 (22:22 +0000)
commitd59638e14f61a5429eb60c7c3630e17dcc888771
tree3ef267b15ba5d0bc99c4d0381dc0612c59adefbctree | snapshot
parent69683f13d27fdfe88c850721938f6a2c2b9d92e2commit | diff
Follow up to 260439, Speculative fix to clang builders

It looks like clang has a couple of test cases which caught the fact LVI was not slightly more precise after 260439.  When looking at the failures, it struck me as wasteful to be querying nullness of a constant via LVI, so instead of tweaking the clang tests, let's just stop querying constants from this source.

llvm-svn: 260451
llvm/lib/Transforms/Scalar/CorrelatedValuePropagation.cpp diff | blob | history
Domain: System / Toolchain;