public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4979: g++ 3.0 & 3.1 compile failes with unable to find register to spill
Date: Fri, 21 Dec 2001 09:16:00 -0000	[thread overview]
Message-ID: <20011221171602.15953.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/4979; it has been noted by GNATS.

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
        tmwg@inxservices.com
Cc:  
Subject: Re: c++/4979: g++ 3.0 & 3.1 compile failes with unable to find register to spill
Date: Fri, 21 Dec 2001 18:23:29 +0100

 Hi,
 
 the ICE can be reproduced with the following small example:
 
 class A
 {
     int i;
     A& f();
 };
 
 A& A::f()
 {
     i/=3;
     return *this;
 }
 
 Just compile the snippet with "g++ -O -fschedule-insns"
 (gcc 3.0.x or 3.1 20011219 on i686-pc-linux-gnu).
 
 Greetings,
 Volker Reichelt
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4979
 
 


             reply	other threads:[~2001-12-21 17:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21  9:16 Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-21 11:06 Mark Mitchell
2002-04-21 11:06 George Garvey
2002-04-21 11:00 mmitchel
2002-04-20 14:02 mmitchel
2002-04-14 11:06 Jason Merrill
2002-04-09  6:05 jason
2002-04-09  5:56 George Garvey
2002-04-09  5:36 Jason Merrill
2002-04-08 17:08 jason
2001-12-03 11:46 rodrigc
2001-12-03 11:40 rodrigc
2001-12-03 11:36 George Garvey
2001-12-03  8:46 rodrigc
2001-12-03  8:39 rodrigc

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=20011221171602.15953.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --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).