public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Robert Boehne <rboehne@ricardo-us.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/4122: undefined reference to `non-virtual thunk to ...' Date: Thu, 10 Jan 2002 07:46:00 -0000 [thread overview] Message-ID: <20020110154604.28450.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/4122; it has been noted by GNATS. From: Robert Boehne <rboehne@ricardo-us.com> To: Michael Ritzert <michael@ritzert.de> Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, juergen@monocerus.demon.co.uk, boehme@informatik.hu-berlin.de, loewis@informatik.hu-berlin.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/4122: undefined reference to `non-virtual thunk to ...' Date: Thu, 10 Jan 2002 09:41:36 -0600 Michael Ritzert wrote: > > It fixes all testcases I have. > > Thanks, > Michael Ritzert > > Am Donnerstag, 10. Januar 2002 07:31 schrieb rodrigc@gcc.gnu.org: > > Synopsis: undefined reference to `non-virtual thunk to ...' > > > > State-Changed-From-To: open->feedback > > State-Changed-By: rodrigc > > State-Changed-When: Wed Jan 9 22:31:33 2002 > > State-Changed-Why: > > The following patch was checked into the gcc 3.1 which > > probably fixes PR 4122: > > http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00465.html > > > > Can you verify that this patch solves the problem for you? > > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc& > >pr=4122 I've checked the 3.0-branch, and this patch fixes all of the test cases.
next reply other threads:[~2002-01-10 15:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-10 7:46 Robert Boehne [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-11 4:49 rodrigc 2002-01-10 5:26 Michael Ritzert 2002-01-09 22:31 rodrigc 2001-12-21 4:56 Nathan Sidwell 2001-12-20 8:16 Robert Boehne 2001-12-19 19:26 Jason Merrill 2001-12-19 18:56 Robert Boehne 2001-12-14 15:16 Robert Boehne 2001-08-25 3:46 michael
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=20020110154604.28450.qmail@sources.redhat.com \ --to=rboehne@ricardo-us.com \ --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: linkBe 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).