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/4238
Date: Wed, 05 Sep 2001 11:46:00 -0000	[thread overview]
Message-ID: <20010905184600.26395.qmail@sourceware.cygnus.com> (raw)

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

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, artem@zavtra.ru
Cc:  
Subject: Re: optimization/4238
Date: Wed, 5 Sep 2001 20:47:44 +0200

 Hi,
 
 a smaller test case for this bug is the following piece of code:
 
 template<class T> struct A
 {
     void f()
     {
         struct B { B(int){} };
         B b(0);
     }
 };
 
 
 void g()
 {
     A<void> a;
     a.f();
 }
 
 
 It crashes gcc 3.0 on a LINUX box as well as gcc 3.0 and the 20010903
 snapshot of gcc 3.0.2 (prerelease) on an IRIX box.
 And you only need -O to get the crash. ;-)
 
 Greetings,
 Volker Reichelt
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4238&database=gcc
 
 


                 reply	other threads:[~2001-09-05 11:46 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=20010905184600.26395.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).