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: optimization/4889
Date: Tue, 13 Nov 2001 19:16:00 -0000	[thread overview]
Message-ID: <20011119201601.13938.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR optimization/4889; 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,
        pgregory@aqsis.com
Cc:  
Subject: Re: optimization/4889
Date: Mon, 19 Nov 2001 21:25:35 +0100

 Hi,
 
 I tried to reduce the size of the provided testcase a little bit
 and distilled the following 3 lines of code that still crash 3.0.2
 (just compile with g++ -O):
 
 double& f();
 struct A { A (int i) { i?f():f(); } };
 A a(1);
 
 In fact they also crash 3.1 (as of 20011112)! So, being able to compile
 the original testcase with 3.1 without errors just seems to be good/bad
 luck.
 
 Greetings,
 Volker Reichelt
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4889&database=gcc
 
 


                 reply	other threads:[~2001-11-19 20:16 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=20011119201601.13938.qmail@sourceware.cygnus.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).