Displaying 3 results from an estimated 3 matches for "novect".
Did you mean:
norect
2012 Apr 03
1
[LLVMdev] pb05 results for current llvm/dragonegg
....3. The benchmarks
for -msse3 and -msse4 appear identical (at least for degg+optnz). This is fortunate
since there seems to be a bug in -msse4 on 2.33 GHz (T7600) Intel Core 2 Duo Merom
(http://llvm.org/bugs/show_bug.cgi?id=12434). I've added two additional entries to
the table. The first, degg+novect+optnz, should show the optimizations achieved by
-fplugin-arg-dragonegg-enable-gcc-optzns in the absence of autovectorization by
FSF gcc. This shows the missing optimization opportunities for LLVM IR-level outside
of autovectorization. The second entry is for the new LLVM autovectorization option
w...
2012 Apr 03
0
[LLVMdev] pb05 results for current llvm/dragonegg
On Tue, 3 Apr 2012 08:57:51 -0400
Jack Howarth <howarth at bromo.med.uc.edu> wrote:
> On Tue, Apr 03, 2012 at 09:26:38AM +0200, Duncan Sands wrote:
> > Hi Jack,
> >
> >> Attached are the Polyhedron 2005 benchmark results for current
> >> llvm/dragonegg svn on x86_64-apple-darwin11 built against Xcode
> >> 4.3.2 and FSF gcc 4.6.3.
> >
>
2012 Apr 03
3
[LLVMdev] pb05 results for current llvm/dragonegg
On Tue, Apr 03, 2012 at 09:26:38AM +0200, Duncan Sands wrote:
> Hi Jack,
>
>> Attached are the Polyhedron 2005 benchmark results for current llvm/dragonegg svn
>> on x86_64-apple-darwin11 built against Xcode 4.3.2 and FSF gcc 4.6.3.
>
> thanks for the numbers. How does this compare to LLVM 3.0 - were there any
> regressions?
The results from just before