This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/35496] [4.4 Regression] test failures between revs. 132950 and 132974
- From: "ubizjak at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Mar 2008 18:16:11 -0000
- Subject: [Bug target/35496] [4.4 Regression] test failures between revs. 132950 and 132974
- References: <bug-35496-12313@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from ubizjak at gmail dot com 2008-03-08 18:16 -------
(In reply to comment #0)
> FAIL: gfortran.dg/array_constructor_12.f90 -O3 -fomit-frame-pointer execution
> test
> FAIL: gfortran.dg/array_constructor_12.f90 -O3 -fomit-frame-pointer
> -funroll-loops execution test
> FAIL: gfortran.dg/array_constructor_12.f90 -O3 -fomit-frame-pointer
> -funroll-all-loops -finline-functions execution test
> FAIL: gfortran.dg/array_constructor_12.f90 -O3 -g execution test
>
> The failures of gfortran.dg/array_constructor_12.f90 result from a segmentation
> fault. All failures disappear with -m64. Between the two builds I have replaced
> the first patch (comment #3) for PR33642 by the second one (comment #4).
This is vectorizer in action. Note that -msse2 is the default for
i686-apple-darwin, and the testcase indeed fails with -O2 -msse2
-ftree-vectorize on linux too.
It looks like wrong assumption for DImode alignment in the vectorizer to me.
Confirmed on linux using "-O2 -msse2 -ftree-vectorize".
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2008-03-08 18:16:11
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35496