From: Nathan Sidwell <nathan@codesourcery.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.0.1 Status Report
Date: Fri, 20 Jul 2001 03:45:00 -0000 [thread overview]
Message-ID: <3B580BD3.BF66E35F@codesourcery.com> (raw)
In-Reply-To: <76410000.995505677@warlock.codesourcery.com>
Mark Mitchell wrote:
>
> We are nearing the pre-3.0.1 freeze.
As we all know, there are still problems with ctor vtables and
polymorphic virtual base class initialization. I have had a look
at some of those, but failed to make headway due to lack of time and
a twisty maze of base class accessor functions. Rather than
battle against the impending deadline to fix these (as we tried
for 3.0), I'm not even going to try. Racing for the deadline
will most surely miss something.
I aim to fix these in 3.1, but first I'm going to remove the
old-abi cruft which is confusing the issue right now.
I have assigned gnats bugs relating to this stuff to me. If anyone
wishes to take them up for 3.0.1, let me know.
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next prev parent reply other threads:[~2001-07-20 3:45 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 18:41 Mark Mitchell
2001-07-19 6:17 ` Joseph S. Myers
2001-07-20 3:45 ` Nathan Sidwell [this message]
2001-07-20 10:26 ` C++ compile-time regressions (was: GCC 3.0.1 Status Report) Gerald Pfeifer
2001-07-20 10:54 ` Nathan Sidwell
2001-07-20 16:41 ` Loren James Rittle
2001-07-23 5:17 ` Gerald Pfeifer
2001-07-23 11:56 ` Daniel Berlin
2001-07-23 2:51 ` Gerald Pfeifer
2001-07-20 10:55 ` Mark Mitchell
2001-07-20 14:22 ` Joe Buck
2001-07-20 16:28 ` Mark Mitchell
2001-07-20 21:05 ` Joe Buck
2001-07-23 10:44 ` Gerald Pfeifer
2001-07-23 11:12 ` Joe Buck
2001-07-23 11:57 ` Gerald Pfeifer
2001-07-23 13:30 ` Joe Buck
2001-07-24 7:18 ` Gerald Pfeifer
2001-07-24 7:55 ` Daniel Berlin
2001-07-24 10:09 ` Joe Buck
2001-07-24 10:19 ` Gabriel Dos Reis
2001-07-24 10:44 ` Joe Buck
2001-07-24 10:56 ` Gabriel Dos Reis
2001-07-24 10:25 ` Daniel Berlin
2001-07-24 10:49 ` Joe Buck
2001-07-24 11:08 ` Daniel Berlin
2001-07-23 14:36 ` Mark Mitchell
2001-07-25 8:06 ` Gerald Pfeifer
2001-08-02 0:20 ` C++ compile-time regressions Gerald Pfeifer
2001-08-02 0:26 ` Mark Mitchell
2001-08-02 11:00 ` aoliva
2001-08-02 12:00 ` Mark Mitchell
2001-08-02 12:26 ` aoliva
2001-08-02 12:37 ` Joe Buck
2001-08-02 12:41 ` Mark Mitchell
2001-08-02 12:48 ` Joe Buck
2001-08-02 13:53 ` Daniel Berlin
2001-08-07 7:54 ` Gerald Pfeifer
2001-07-23 11:54 ` C++ compile-time regressions (was: GCC 3.0.1 Status Report) Daniel Berlin
2001-07-23 12:42 ` Bernd Schmidt
2001-07-23 12:50 ` law
2001-07-23 13:15 ` Daniel Berlin
2001-07-23 14:00 ` law
2001-07-20 10:57 ` Daniel Berlin
2001-07-20 14:20 ` Joe Buck
2001-07-25 17:52 ` GCC 3.0.1 Status Report Marc Espie
2001-08-13 23:15 ` Mark Mitchell
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=3B580BD3.BF66E35F@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).