From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-21379-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 21168 invoked by alias); 26 Aug 2002 12:56:02 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 21154 invoked by uid 71); 26 Aug 2002 12:56:01 -0000
Date: Mon, 26 Aug 2002 06:56:00 -0000
Message-ID: <20020826125601.21153.qmail@sources.redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
From: Tim Prince <tprince@computer.org>
Subject: Re: c/7723: Internal compiler error - Pentium3 sse - gcc 3.2
Reply-To: Tim Prince <tprince@computer.org>
X-SW-Source: 2002-08/txt/msg00550.txt.bz2
List-Id: <gcc-prs.sourceware.org>

The following reply was made to PR middle-end/7723; it has been noted by GNATS.

From: Tim Prince <tprince@computer.org>
To: morandini@aero.polimi.it, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/7723: Internal compiler error - Pentium3 sse - gcc 3.2
Date: Mon, 26 Aug 2002 05:52:13 -0700

 On Monday 26 August 2002 03:01, morandini@aero.polimi.it wrote:
 > >Number:         7723
 > >Category:       c
 > >Synopsis:       Internal compiler error - Pentium3 sse - gcc 3.2
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          ice-on-legal-code
 > 
 > >Description:
 >
 > 1)
 > with this code:
 > /*-------------------*/
 > typedef int v4sf __attribute__ ((mode(V4SF)));
 > int main(void) {
 > 	v4sf a={0.,0.,0.,0.};
 > 	return 0;
 > };
 > /*------------------*/
 >
 > marco@pc-31c:~> gcc -msse -march=pentium3 -mfpmath=sse main1.c: In function
 > `main': main1.c:5: Internal compiler error in instantiate_virtual_regs_1,
 > at function.c:3972
 >
 > 2)this code is compiled, but the program gives a SIGSEGV. What's wrong?
 > (binutils  2.13.90.0.4 20020814)
 > /*------------------*/
 > typedef int v4sf __attribute__ ((mode(V4SF)));
 > int main(void) {
 > 	v4sf a={1.,1.,1.,1.};
 > 	v4sf b={2.,2.,2.,2.};
 > 	v4sf c;
 > 	c=__builtin_ia32_addss (a, b);
 > 	return 0;
 > };
 Some might argue about characterizing this as "legal code."  Perhaps it 
 should be flagged as an error.  gcc doesn't support alignment in main(), so 
 it seems that any code which is not standard C and depends on alignment might 
 not be "legal."
 -- 
 Tim Prince