This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/17589] segfault while running code compiled with -ftree-vectorize
- From: "berndtrog at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Sep 2004 16:37:38 -0000
- Subject: [Bug tree-optimization/17589] segfault while running code compiled with -ftree-vectorize
- References: <20040921180641.17589.berndtrog@yahoo.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From berndtrog at yahoo dot com 2004-09-22 16:37 -------
Hmm, now I've used -D "2004-09-17 00:00:00" for the checkout.
It still segfaults:
When I use gdb to run it, I get:
Program received signal SIGSEGV, Segmentation fault.
0x080484a7 in main1 ()
1: x/i $eip 0x80484a7 <main1+87>: movdqa (%edx),%xmm0
(gdb) info registers
eax 0x1 1
ecx 0xbffff3c4 -1073744956
edx 0xbffff3c4 -1073744956
^
According to http://developer.intel.com/design/Pentium4/manuals/25366614.pdf,
when the source or destination operand is a memory operand, the operand must be
aligned on a 16-byte boundary or a general-protection exception (#GP) will be
generated.
Could this be OS related? (I'm using Linux 2.4.25, CONFIG_MPENTIUM4=y)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589