This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/34038] 176.gcc segfaults when compiled with -O2 -ftree-vectorize -maltivec
- From: "janis at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Dec 2007 19:22:55 -0000
- Subject: [Bug tree-optimization/34038] 176.gcc segfaults when compiled with -O2 -ftree-vectorize -maltivec
- References: <bug-34038-4503@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from janis at gcc dot gnu dot org 2007-12-12 19:22 -------
The failure goes away with -mabi=altivec, which is not the default with -m32.
I had never seen this failure in my earlier testing on powerpc64-linux because
whenever I used -maltivec I also used -mabi=altivec. It's not clear to me if
it's legitimate to use -maltivec, or -mcpu with machines that imply -maltivec,
without also using -mabi=altivec when the code will use AltiVec registers.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34038