[Bug target/50150] misc vect.exp failures for target arm

2011-09-25 Thread carrot at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50150

--- Comment #4 from Carrot carrot at google dot com 2011-09-26 02:16:15 UTC 
---
After adding '--with-fpu=neon' '--with-float=softfp' to my configuration, most
of the failure disappeared, but there are still several

gcc
FAIL: gcc.dg/vect/vect-120.c scan-tree-dump-times vect vectorized 1 loops 1
FAIL: gcc.dg/vect/slp-perm-8.c execution test
FAIL: gcc.dg/vect/vect-120.c -flto scan-tree-dump-times vect vectorized 1
loops 1
FAIL: gcc.dg/vect/slp-perm-8.c -flto execution test

g++
FAIL: g++.dg/vect/pr36648.cc scan-tree-dump-times vect vectorized 1 loops 1
FAIL: g++.dg/vect/pr36648.cc scan-tree-dump-times vect vectorizing stmts using
SLP 1


[Bug target/50150] misc vect.exp failures for target arm

2011-09-13 Thread ramana at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50150

Ramana Radhakrishnan ramana at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2011-09-13
 Ever Confirmed|0   |1

--- Comment #3 from Ramana Radhakrishnan ramana at gcc dot gnu.org 2011-09-13 
07:29:09 UTC ---
That's then an inconsistency in the test infrastructure in the non
--with-fpu=neon --with-float=softfp configuration case.


[Bug target/50150] misc vect.exp failures for target arm

2011-08-22 Thread ramana at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50150

Ramana Radhakrishnan ramana at gcc dot gnu.org changed:

   What|Removed |Added

 CC||ramana at gcc dot gnu.org

--- Comment #1 from Ramana Radhakrishnan ramana at gcc dot gnu.org 2011-08-22 
20:42:16 UTC ---
So how was this toolchain configured by default ? 

Ramana


[Bug target/50150] misc vect.exp failures for target arm

2011-08-22 Thread carrot at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50150

--- Comment #2 from Carrot carrot at google dot com 2011-08-23 01:14:46 UTC 
---
(In reply to comment #1)
 So how was this toolchain configured by default ? 
 
 Ramana

My configuration is:


configured by /usr/local/google/home/carrot/trunk4/configure, generated by GNU
Autoconf 2.64,
  with options \ '--build=x86_64-build_pc-linux-gnu'
'--host=x86_64-build_pc-linux-gnu' '--target=arm-unknown-linux-gnueabi'
'--with-sysroot=/home/carrot/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sys-root'
'--disable-multilib' '--with-float=soft' '--disable-sjlj-exceptions'
'--enable-__cxa_atexit' '--disable-nls' '--enable-threads=posix'
'--enable-symvers=gnu' '--enable-c99' '--enable-long-long'
'--enable-target-optspace' '--disable-bootstrap'
'build_alias=x86_64-build_pc-linux-gnu' 'host_alias=x86_64-build_pc-linux-gnu'
'target_alias=arm-unknown-linux-gnueabi' '--enable-languages=c,c++,lto'\