public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Uros Bizjak <uros@kss-loka.si>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/7151: ICE when compiling for UltraSPARC
Date: Thu, 06 Feb 2003 13:16:00 -0000	[thread overview]
Message-ID: <20030206131600.21688.qmail@sources.redhat.com> (raw)

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

From: Uros Bizjak <uros@kss-loka.si>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, gawrilow@math.TU-Berlin.DE
Cc:  
Subject: Re: middle-end/7151: ICE when compiling for UltraSPARC
Date: Thu, 06 Feb 2003 14:05:06 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7151
 
    This bug is not fixed in 3.2.2 release. PR7151 and PR8281 describe 
 the same bug (PR8281 has a nice testcase included, PR8654 has another 
 testcase for the same problem) and with gcc 3.2.2 I got segmentation 
 fault instead of ICE in line 43:
 
  > gcc -O2 -c -fPIC -mcpu=ultrasparc 8281.c
 8281.c: In function `__ieee754_pow':
 8281.c:43: internal error: Segmentation Fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions
 
  > gcc -v
 Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.2.2/specs
 Configured with: ../gcc-3.2.2/configure --with-gnu-ld
 Thread model: posix
 gcc version 3.2.2
 
 	Uros.
 


             reply	other threads:[~2003-02-06 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:16 Uros Bizjak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-01 20:54 davem
2002-06-28  2:46 gawrilow

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=20030206131600.21688.qmail@sources.redhat.com \
    --to=uros@kss-loka.si \
    --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).