llvm/lib/Transforms/Vectorize, branch testinghttp://llvm.orghttps://git.amat.us/llvm/atom/lib/Transforms/Vectorize?h=testing2013-03-14T18:54:36ZLoopVectorize: Invert case when we use a vector cmp value to query select cost2013-03-14T18:54:36ZArnold Schwaighoferaschwaighofer@apple.com2013-03-14T18:54:36Zurn:sha1:d517da33b712b5d8d687ee5e5974056a4787ec4f
We generate a select with a vectorized condition argument when the condition is
NOT loop invariant. Not the other way around.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177098 91177308-0d34-0410-b5e6-96231b3b80d8
BBVectorize: Fixup debugging statements2013-03-10T20:57:42ZHal Finkelhfinkel@anl.gov2013-03-10T20:57:42Zurn:sha1:76a05c93b13a8debec4497a6e4e753d7531709e5
After the recent data-structure improvements, a couple of debugging statements
were broken (printing pointer values).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176791 91177308-0d34-0410-b5e6-96231b3b80d8
Remove a source of nondeterminism from the LoopVectorizer.2013-03-09T19:22:40ZBenjamin Kramerbenny.kra@googlemail.com2013-03-09T19:22:40Zurn:sha1:0d932717d8d22b0e747b15fddea2c718043e4d51
This made us emit runtime checks in a random order. Hopefully bootstrap
miscompares will go away now.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176775 91177308-0d34-0410-b5e6-96231b3b80d8
LoopVectorizer: Ignore all dbg intrinisic2013-03-09T16:27:27ZArnold Schwaighoferaschwaighofer@apple.com2013-03-09T16:27:27Zurn:sha1:738295e4570f502360c11bc51843f5a8516a9526
Ignore all DbgIntriniscInfo instructions instead of just DbgValueInst.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176769 91177308-0d34-0410-b5e6-96231b3b80d8
LoopVectorizer: Ignore dbg.value instructions2013-03-09T15:56:34ZArnold Schwaighoferaschwaighofer@apple.com2013-03-09T15:56:34Zurn:sha1:56ee544a3af2b019329f06422c00e8a3645b895c
We want vectorization to happen at -g. Ignore calls to the dbg.value intrinsic
and don't transfer them to the vectorized code.
radar://13378964
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176768 91177308-0d34-0410-b5e6-96231b3b80d8
Insert the reduction start value into the first bypass block to preserve domination.2013-03-08T16:58:37ZBenjamin Kramerbenny.kra@googlemail.com2013-03-08T16:58:37Zurn:sha1:f22d9cfa6d145ce26930804cc3ac54340f49c38b
Fixes PR15344.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176701 91177308-0d34-0410-b5e6-96231b3b80d8
PR14448 - prevent the loop vectorizer from vectorizing the same loop twice.2013-03-02T01:33:49ZNadav Rotemnrotem@apple.com2013-03-02T01:33:49Zurn:sha1:5290baacb8ca4fb75d798e873a441cad11cbfb2c
The LoopVectorizer often runs multiple times on the same function due to inlining.
When this happens the loop vectorizer often vectorizes the same loops multiple times, increasing code size and adding unneeded branches.
With this patch, the vectorizer during vectorization puts metadata on scalar loops and marks them as 'already vectorized' so that it knows to ignore them when it sees them a second time.
PR14448.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176399 91177308-0d34-0410-b5e6-96231b3b80d8
LoopVectorize: Don't hang forever if a PHI only has skipped PHI uses.2013-03-01T19:07:31ZBenjamin Kramerbenny.kra@googlemail.com2013-03-01T19:07:31Zurn:sha1:5d79bb8770a5a655af0dccc87b952c3ea9bad45e
Fixes PR15384.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176366 91177308-0d34-0410-b5e6-96231b3b80d8
LoopVectorize: Vectorize math builtin calls.2013-02-27T15:24:19ZBenjamin Kramerbenny.kra@googlemail.com2013-02-27T15:24:19Zurn:sha1:2fe71f8f7e678174ba217d3d16525092805ad45b
This properly asks TargetLibraryInfo if a call is available and if it is, it
can be translated into the corresponding LLVM builtin. We don't vectorize sqrt()
yet because I'm not sure about the semantics for negative numbers. The other
intrinsic should be exact equivalents to the libm functions.
Differential Revision: http://llvm-reviews.chandlerc.com/D465
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176188 91177308-0d34-0410-b5e6-96231b3b80d8
Allow GlobalValues to vectorize with AliasAnalysis2013-02-21T22:39:03ZRenato Golinrenato.golin@linaro.org2013-02-21T22:39:03Zurn:sha1:e18bce5317ff9f64b3c02418f28c6d383d88b294
Storing the load/store instructions with the values
and inspect them using Alias Analysis to make sure
they don't alias, since the GEP pointer operand doesn't
take the offset into account.
Trying hard to not add any extra cost to loads and stores
that don't overlap on global values, AA is *only* calculated
if all of the previous attempts failed.
Using biggest vector register size as the stride for the
vectorization access, as we're being conservative and
the cost model (which calculates the real vectorization
factor) is only run after the legalization phase.
We might re-think this relationship in the future, but
for now, I'd rather be safe than sorry.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@175818 91177308-0d34-0410-b5e6-96231b3b80d8