public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* c/7723: Internal compiler error - Pentium3 sse - gcc 3.2
@ 2002-08-26  5:38 morandini
  0 siblings, 0 replies; 4+ messages in thread
From: morandini @ 2002-08-26  5:38 UTC (permalink / raw)
  To: gcc-gnats


>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
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 26 03:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     morandini@aero.polimi.it
>Release:        gcc version 3.2
>Organization:
>Environment:
SuSE Linux 8.0, kernle 2.4.18, dual pentiun 3
gcc -v:
Reading specs from /home2/marco/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
Configured with: ../configure --enable-threads=posix --enable-languages=c,c++,f77 --prefix=/home2/marco/local : (reconfigured) ../configure --enable-languages=c,c++,f77 --enable-__cxa_atexit --prefix=/home2/marco/local : (reconfigured) ../configure --enable-languages=c,c++,f77 --enable-__cxa_atexit --prefix=/home2/marco/local
Thread model: posix
gcc version 3.2
>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;
};
/*----------------*/

Here is the assembly of the second program:
        .file   "main.c"
        .text
        .align 2
.globl main
        .type   main,@function
main:
        pushl   %ebp
        movl    %esp, %ebp
        subl    $56, %esp
        andl    $-16, %esp
        movl    $0, %eax
        subl    %eax, %esp
        movl    $0x3f800000, -24(%ebp)
        movl    $0x3f800000, -20(%ebp)
        movl    $0x3f800000, -16(%ebp)
        movl    $0x3f800000, -12(%ebp)
        movl    $0x40000000, -40(%ebp)
        movl    $0x40000000, -36(%ebp)
        movl    $0x40000000, -32(%ebp)
        movl    $0x40000000, -28(%ebp)
        movaps  -24(%ebp), %xmm0
        addss   -40(%ebp), %xmm0
        movaps  %xmm0, -56(%ebp)
        movl    $0, %eax
        leave
        ret
.Lfe1:
        .size   main,.Lfe1-main
        .ident  "GCC: (GNU) 3.2"
>How-To-Repeat:
see description
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: c/7723: Internal compiler error - Pentium3 sse - gcc 3.2
@ 2002-08-27  1:47 Tim Prince
  0 siblings, 0 replies; 4+ messages in thread
From: Tim Prince @ 2002-08-27  1:47 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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

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

 On Monday 26 August 2002 07:19, Marco Morandini wrote:
 > Tim Prince wrote:
 > > 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."
 >
 > Opsss.....
 > Yes, I do not get the SIGSEGV after moving everything to a function
 > (If I understand correctly your answer, but I'm definitely not a
 > good programmer)
 >
 > However, I'm still getting the ICE with this:
 > /*-------------------*/
 > typedef int v4sf __attribute__ ((mode(V4SF)));
 > void dummy(void) {
 > 	v4sf c={0.,0.,0.,0.};
 > 	return;
 > };
 > /*-----------------*/
 >
 >
 > Perhaps I'm simply not smart enough to use SIMD gcc support :(
 
 -- 
 Tim Prince


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: c/7723: Internal compiler error - Pentium3 sse - gcc 3.2
@ 2002-08-26  8:36 Marco Morandini
  0 siblings, 0 replies; 4+ messages in thread
From: Marco Morandini @ 2002-08-26  8:36 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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

From: Marco Morandini <morandini@aero.polimi.it>
To: tprince@computer.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/7723: Internal compiler error - Pentium3 sse - gcc 3.2
Date: Mon, 26 Aug 2002 16:19:06 +0200

 Tim Prince wrote:
 > 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."
 
 
 Opsss.....
 Yes, I do not get the SIGSEGV after moving everything to a function
 (If I understand correctly your answer, but I'm definitely not a
 good programmer)
 
 However, I'm still getting the ICE with this:
 /*-------------------*/
 typedef int v4sf __attribute__ ((mode(V4SF)));
 void dummy(void) {
 	v4sf c={0.,0.,0.,0.};
 	return;
 };
 /*-----------------*/
 
 
 Perhaps I'm simply not smart enough to use SIMD gcc support :(
 


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: c/7723: Internal compiler error - Pentium3 sse - gcc 3.2
@ 2002-08-26  6:56 Tim Prince
  0 siblings, 0 replies; 4+ messages in thread
From: Tim Prince @ 2002-08-26  6:56 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-08-27  5:36 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-08-26  5:38 c/7723: Internal compiler error - Pentium3 sse - gcc 3.2 morandini
2002-08-26  6:56 Tim Prince
2002-08-26  8:36 Marco Morandini
2002-08-27  1:47 Tim Prince

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).