Hi,
I’ve been working on the vectorization diagnostics a little more. The first
patch makes sure the analysis diagnostics are printed unless a disabling hint
is provided. And the two pairs of LLVM and Clang patches make the diagnostic
messages easier to understand and extend the
Author: tnowicki
Date: Mon Aug 10 17:17:40 2015
New Revision: 244517
URL: http://llvm.org/viewvc/llvm-project?rev=244517view=rev
Log:
Make frontend floating-point commutivity test X86 specific to avoid cost-model
related problems on arm-thumb and hexagon.
Modified:
Author: tnowicki
Date: Mon Aug 10 18:05:16 2015
New Revision: 244526
URL: http://llvm.org/viewvc/llvm-project?rev=244526view=rev
Log:
Append options for vectorization when pointer checking threshold is exceeded.
Following one of the appended options will allow the loop to be vectorized. We
do
Author: tnowicki
Date: Mon Aug 10 20:10:08 2015
New Revision: 244556
URL: http://llvm.org/viewvc/llvm-project?rev=244556view=rev
Log:
Print vectorization analysis when loop hint is specified.
This patche and a related llvm patch solve the problem of having to explicitly
enable analysis when
Hi Hal, Mark,
These patches solve the problem of having to explicitly enable analysis when
specifying a loop hint pragma to get the diagnostics. Passing AlwasyPrint as
the pass name (see below) causes the front-end to print the diagnostic if the
user has specified '-Rpass-analysis' without an
Author: tnowicki
Date: Mon Aug 10 20:54:48 2015
New Revision: 244561
URL: http://llvm.org/viewvc/llvm-project?rev=244561view=rev
Log:
Make the analysis reporting test with x86 to fix the hexagon build.
Modified:
cfe/trunk/test/Frontend/optimization-remark-analysis.c
Modified:
Author: tnowicki
Date: Thu Aug 27 13:58:34 2015
New Revision: 246189
URL: http://llvm.org/viewvc/llvm-project?rev=246189view=rev
Log:
Improve options printed on vectorization analysis diagnostics.
The LLVM patch changes the analysis diagnostics produced when loops with
Hi Michael, Hal,
Sorry it has been a while since I looked at this. My memory is a little
fuzzy. The intent of 'assume_safety' is to tell LAA to skip dependency
checking on loads and stores so the vectorizer doesn't stop as soon as it
sees both in a loop. At the time 'assume_safety' was
Sorry if this is answered in the patches but what happens if a loop has
both #pragma clang loop and transform defined before it? I guess it
probably shouldn't work.
Perhaps instead you could create a new option to indicate that the order
should be respected.
#pragma clang loop respect_order <-
