search for: vector_select

...size foo, .-foo Some failing tests have now gotten better error reporting than before: $ llvm-as < test/CodeGen/Generic/select-cc.ll | llc Formal argument #0 has unhandled type i64 Stack dump: 0. Program arguments: llc 1. Running pass 'ARM Instruction Selection' on function '@vector_select' Aborted $ llvm-as < test/CodeGen/X86/dagcombine-buildvector.ll | llc Formal argument #1 has unhandled type i64 Stack dump: 0. Program arguments: llc 1. Running pass 'ARM Instruction Selection' on function '@test' Aborted I have tested this on a overo-earth ti omap3 h...

With current dragonegg svn, the Polyhedron 2005 benchmarks all now pass when using the compiler plugin under FSF gcc 4.6.1 on x86_64-apple-darwin11. The differences between the runtime and compile times when using the same plugin under FSF gcc 4.5.4svn are small. Once new vector_select feature is available in llvm and -fplugin-arg-dragonegg-enable-gcc-optzns supports -ftree-vectorizer we might see more of a difference between the two FSF gcc releases. -ffast-math -funroll-loops -msse3 -O3 Runtime Benchmark gcc 4.5.4 gcc 4.6.1 ac 12.19 10...

...28.60 29.39 protein 38.36 39.08 39.98 rnflow 27.28 28.19 31.90 test_fpu 11.43 11.17 11.50 tfft 1.91 1.95 2.16 Mean 12.72 12.62 14.71 Once vector_select() is implemented we can retest without -fno-tree-vectorize.

Hello Evan and Robert I have been investigating the unexpected test failures from the ARM nightly builders in order to get a better picture why the ARM backend don't pass the whole testsuite: I have run the failing tests manually on my arm board and can now categorize most of the thirteen unexpected CodeGen failures in four categories: 1. llvm don't lower MVT::i64 properly on arm

...mask and the consumer of the mask are in different basic blocks. The legalizer works on one basic block at a time. This makes it impossible for the legalizer to find the 'native' representation. I wrote down some of the comments which were made in this email thread: http://wiki.llvm.org/Vector_select Cheers, Nadav -----Original Message----- From: David A. Greene [mailto:greened at obbligato.org] Sent: Thursday, March 10, 2011 18:57 To: Rotem, Nadav Cc: David A. Greene; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Vector select/compare support in LLVM "Rotem, Nadav" <nadav.ro...

...in 38.36 39.08 39.98 > rnflow 27.28 28.19 31.90 > test_fpu 11.43 11.17 11.50 > tfft 1.91 1.95 2.16 > > Mean 12.72 12.62 14.71 > > Once vector_select() is implemented we can retest without -fno-tree-vectorize. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...39.98 > > rnflow 27.28 28.19 31.90 > > test_fpu 11.43 11.17 11.50 > > tfft 1.91 1.95 2.16 > > > > Mean 12.72 12.62 14.71 > > > > Once vector_select() is implemented we can retest without -fno-tree-vectorize. > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > &...

...> rnflow 27.28 28.19 31.90 >>> test_fpu 11.43 11.17 11.50 >>> tfft 1.91 1.95 2.16 >>> >>> Mean 12.72 12.62 14.71 >>> >>> Once vector_select() is implemented we can retest without -fno-tree-vectorize. >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/...

After wasting an inordinate amount of time trying to get test-suite to run on arm-apple-darwin so I could reproduce your results, attached is a patch that fixes the small copy&paste error of having 8-byte alignment for stack-allocated f64s instead of the proper 4-byte. I've updated the patch to the top of trunk changes as well. deep On Fri, Feb 27, 2009 at 8:31 PM, Sandeep Patel

"Rotem, Nadav" <nadav.rotem at intel.com> writes: > One of the arguments for packing masks is that it reduces > vector-registers pressure. Auto-vectorizing compilers maintain > multiple masks for different execution paths (for each loop nesting, > etc). Saving masks in xmm registers may result in vector-register > pressure which will cause spilling of these

...28 28.19 31.90 >>>> test_fpu 11.43 11.17 11.50 >>>> tfft 1.91 1.95 2.16 >>>> >>>> Mean 12.72 12.62 14.71 >>>> >>>> Once vector_select() is implemented we can retest without -fno-tree-vectorize. >>>> >>>> _______________________________________________ >>>> LLVM Developers mailing list >>>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>>> http://lists.cs.uiuc.e...

Hi David, The MOVMSKPS instruction is cheap (2 cycles). Not to be confused with VMASKMOV, the AVX masked move, which is expensive. One of the arguments for packing masks is that it reduces vector-registers pressure. Auto-vectorizing compilers maintain multiple masks for different execution paths (for each loop nesting, etc). Saving masks in xmm registers may result in vector-register

...28 28.19 31.90 >>>> test_fpu 11.43 11.17 11.50 >>>> tfft 1.91 1.95 2.16 >>>> >>>> Mean 12.72 12.62 14.71 >>>> >>>> Once vector_select() is implemented we can retest without -fno-tree-vectorize. >>>> >>>> _______________________________________________ >>>> LLVM Developers mailing list >>>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>>> http://lists.cs.uiuc.e...

I'm not currently setup to be able to run the A/B comparison tests that test-suite relies upon. Fhourstones-3.1 looks to be the simplest. If you can send me the two .o files from either EABI or Darwin, I can dig into why this went wrong for you. deep On Thu, Feb 26, 2009 at 3:53 PM, Evan Cheng <echeng at apple.com> wrote: > Sorry I haven't gotten back to you earlier. I have