[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-05-18 Thread ghazi at gcc dot gnu dot org
--- Comment #8 from ghazi at gcc dot gnu dot org 2007-05-19 06:02 --- fixed: http://gcc.gnu.org/ml/gcc-testresults/2007-05/msg00150.html by this patch: http://gcc.gnu.org/ml/gcc-patches/2007-04/msg01733.html -- ghazi at gcc dot gnu dot org changed: What|Removed

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-25 Thread dorit at il dot ibm dot com
--- Comment #7 from dorit at il dot ibm dot com 2007-04-25 21:30 --- > Are you going to submit/install your patch? yes, I'll go ahead and submit the patch -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31615

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-25 Thread ghazi at gcc dot gnu dot org
--- Comment #6 from ghazi at gcc dot gnu dot org 2007-04-25 18:14 --- (In reply to comment #5) > ah, ok. so, in that case we probably want to just change the '3' to '2' in the > above test: > Index: testsuite/gfortran.dg/vect/vect-5.f90 > =

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-18 Thread dorit at il dot ibm dot com
--- Comment #5 from dorit at il dot ibm dot com 2007-04-19 07:27 --- (In reply to comment #4) > (In reply to comment #3) > > But then I wonder why we don't see the same failure on ia64? > Because the failing part of the testcase is only done on ilp32 targets: > ! { dg-final { scan-tree-d

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-18 Thread ghazi at gcc dot gnu dot org
--- Comment #4 from ghazi at gcc dot gnu dot org 2007-04-19 05:11 --- (In reply to comment #3) > But then I wonder why we don't see the same failure on ia64? Because the failing part of the testcase is only done on ilp32 targets: ! { dg-final { scan-tree-dump-times "Alignment of access

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-18 Thread dorit at il dot ibm dot com
--- Comment #3 from dorit at il dot ibm dot com 2007-04-18 10:18 --- > Created dump file using -fdump-tree-vect-details thanks. So I don't understand why we expect to version for 3 different data-references, since there are only 2 in the loop that is vectorized. But then I wonder why we

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-17 Thread ghazi at gcc dot gnu dot org
--- Comment #2 from ghazi at gcc dot gnu dot org 2007-04-18 07:05 --- Created an attachment (id=13387) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13387&action=view) Dump file using -fdump-tree-vect-details Created dump file using -fdump-tree-vect-details -- http://gcc.gnu.

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-17 Thread dorit at il dot ibm dot com
--- Comment #1 from dorit at il dot ibm dot com 2007-04-18 06:42 --- could you please provide the .vect dump file, as generated with -fdump-tree-vect-details? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31615

[Bug fortran/31615] testsuite failure in gfortran.dg/vect/vect-5.f90

2007-04-17 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last recon