public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7910: [cygwin] Seg fault of g++ 3.2 when compiling OpenSceneGraph 0.9.1
Date: Sun, 06 Apr 2003 23:06:00 -0000	[thread overview]
Message-ID: <20030406230601.22234.qmail@sources.redhat.com> (raw)

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

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<o.lauffenburger@topsolid.com>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>
Cc: "Wolfgang Bangerth" <bangerth@ices.utexas.edu>
Subject: Re: c++/7910: [cygwin] Seg fault of g++ 3.2 when compiling OpenSceneGraph 0.9.1
Date: Mon, 7 Apr 2003 01:05:21 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
 r=7910
 
 I can reproduce this only with 3.3 (20030401). Redux is:
 
 ---------------------------------------------
 class __attribute__((dllimport)) Foo
 {
    public:
         virtual void dummy_foo_func(void)
         {}
 };
 
 class Bar : public Foo
 {
     public:
         ~Bar();
         void dummy_bar_func();
 };
 
 Bar::~Bar()
 {}
 
 void Bar::dummy_bar_func()
 {}
 ---------------------------------------------
 pr7910.cpp:20: internal compiler error: Segmentation fault
 Please submit a full bug report,
 
 Notice that Bar's destructor and the other dummy function _must_ be defined
 out of the class definition for the ICE to happen. 2.95, 3.2 and 3.2.2
 compile the code correctly. I can't test with 3.4 (mainline broken for
 cygwin).
 
 3.3 regression only.
 
 Giovanni Bajo
 


                 reply	other threads:[~2003-04-06 23:06 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=20030406230601.22234.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --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).