public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: target/1613&Body=http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1613&database=gcc
Date: Thu, 30 Aug 2001 12:56:00 -0000	[thread overview]
Message-ID: <20010830195601.8208.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR target/1613; it has been noted by GNATS.

From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, soka@line.co.jp
Cc:  
Subject: Re: target/1613&Body= http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1613&database=gcc
Date: Thu, 30 Aug 2001 21:52:30 +0200

 Hi,
 
 I just got a gcc-3.0.1 ICE in the same place (emit-rtl.c:542) on
 sparc-sun-solaris2.8 (ultrasparc) with this code:
 
 void foo(a, b, c, d, e, f, g, h, i, j, k, l, m, n, o)
   double a, b, c, d, e, f, g, h, i, j, k, l, m, n, o;
 {
   bar(a,b,c,d,e,f,g,h,i,j,k,l,m,n,o, a+b+c+d+e+f+g+h+i+j+k+l+m+n+o);
 }
 
 $ gcc3 -O2 -mcpu=ultrasparc -S -xcpp-output Bug.i 
 Bug.i: In function `foo':
 Bug.i:5: Internal compiler error in gen_reg_rtx, at emit-rtl.c:542
 
 
 However, foo.c doesn't crash gcc-3.0.1 on solaris.
 I can't test it linux now; maybe the original submitter can.
 
 PR 2099 is another case, this one for gcc version 3.1 20010226
 (experimental) on ultrasparc.  It crashes gcc-3.0.1 -O3 -mcpu=ultrasparc
 too.  It does not crash with -O2 instead of -O3.
 
 My gcc (which bootstrapped fine, with CC=gcc-2.95.3):
 
 host: sparc-sun-solaris2.8
 build: sparc-sun-solaris2.8
 target: sparc-sun-solaris2.8
 configured with: ../gcc-3.0.1/configure --prefix=/usit/bombur/hbf --program-suffix=3 --enable-version-specific-runtime-libs --enable-languages=c --quiet
 
 -- 
 Hallvard


                 reply	other threads:[~2001-08-30 12:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010830195601.8208.qmail@sourceware.cygnus.com \
    --to=h.b.furuseth@usit.uio.no \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).