[Bug c/17589] New: segfault while running code compiled with -ftree-vectorize

[Bug c/17589] New: segfault while running code compiled with -ftree-vectorize

[berndtrog at yahoo dot com]

When I try to run vect-2 from testsuite I get a segfault.

I've used "gcc -O2 -ftree-vectorize -msse2 vect-2.c -o vect-2 -Wall" to
compile vect-2.c.

gcc version 4.0.0 20040921 (experimental)

hw: P4 Northwood

-- 
           Summary: segfault while running code compiled with -ftree-
                    vectorize
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: berndtrog at yahoo dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-linux
  GCC host triplet: i686-linux
GCC target triplet: i686-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug c/17589] segfault while running code compiled with -ftree-vectorize

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-09-21 18:53 -------
Can you attch the preprocessed source.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug tree-optimization/17589] segfault while running code compiled with -ftree-vectorize

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
          Component|c                           |tree-optimization


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug tree-optimization/17589] segfault while running code compiled with -ftree-vectorize

[berndtrog at yahoo dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug tree-optimization/17589] segfault while running code compiled with -ftree-vectorize

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-09-22 13:00 -------
I cannot reproduce it on either: "3.5.0 20040909" or "4.0.0 20040917".

Hmm, main1 should not be inlined into main....



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug tree-optimization/17589] segfault while running code compiled with -ftree-vectorize

[berndtrog at yahoo dot com]

------- 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

[Bug target/17589] segfault while running code compiled with -ftree-vectorize

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-09-22 17:31 -------
This is a target problem.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|tree-optimization           |target
           Keywords|                            |wrong-code


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug target/17589] segfault while running code compiled with -ftree-vectorize

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-09-22 17:31 -------
As it is right on powerpc and the tree dumps are correct.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug target/17589] segfault while running code compiled with -ftree-vectorize

[berndtrog at yahoo dot com]

------- Additional Comments From berndtrog at yahoo dot com  2004-09-24 15:18 -------
Can anyone reproduce the problem on i686-linux (P4)?



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug target/17589] segfault while running code compiled with -ftree-vectorize

[dorit at il dot ibm dot com]

------- Additional Comments From dorit at il dot ibm dot com  2004-10-27 11:48 -------
(In reply to comment #7)
> Can anyone reproduce the problem on i686-linux (P4)?

I wasn't able to reporoduce it on i686-pc-linux-gnu.

This might be related to PR18173.

Is PREFERRED_STACK_BOUNDARY != STACK_BOUNDARY in the platform in question? 
maybe that's the problem? (this deson't seem to be the problem thought in 
PR18173).



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug target/17589] segfault while running code compiled with -ftree-vectorize

[berndtrog at yahoo dot com]

------- Additional Comments From berndtrog at yahoo dot com  2004-10-27 15:56 -------
Hmm, there seems to be a relation between the
version of glibc an this bug:

glibc-2.2 segfault
glibc-2.2.5 NO segfault
glibc-2.3.3 NO segfault

Can anyone try 
make check-gcc RUNTESTFLAGS="vect.exp" 
with an old distribution(glibc-2.2) on a sse2 system?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589

[Bug target/17589] segfault while running code compiled with -ftree-vectorize

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-09-24 16:55 -------
This is a glibc issue and nothing else.

Closing as invalid.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17589