GCC 3.0

[Mark Mitchell <mark at codesourcery dot com>]

Since I have spent so little time on GCC in the last few weeks, a lot
of you have probably been wondering if I have been abducted by aliens.

I have been -- but that's another story. :-)

I've been swamped with personal and professional tasks, and then the
holidays, and ...

However, I have now complete cleared the boards -- my only technical
task is now GCC.

Obviously, I will be focusing most of my energy on the GCC 3.0
release.

I would like to branch in the relatively near future.  I know of only
one major feature outstanding, after a recent pow-wow between Kosnik,
Henderson, Keating, Petit-Bianco, and myself:

  - Richard is going to make a driver switch to control whether or not
    we use libgcc.so.

There is one optional feature, that I do not think we need to hold up
branching for:

  - Adopting the high-level IA64 ABI EH model, rather than the current
    run-time interface.

I'm sure there are many remaining technical problems.  

  - Does V3 work on the major architectures yet, or are we still hung
    up on AIX and HPUX?

  - Other major functional failures?

I'm looking for major pieces of missing functionality that would
prevent branching, not just bugs, however serious.

Richard, what's a reasonable time-frame for the driver switch?

In the meantime, I'm working on compile-time performance stuff.  On
the way back from Nashville, I knoced another few percent off on C++
testcase; patches coming soon...

Assume that I'm out of touch with GCC mail not sent to me personally
-- I couldn't keep up with the lists the last couple of weeks.  If
there's something you think I should be aware of, feel free to zap it
to me directly -- no need to copy the lists.

Sorry for the long absence,
  
--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com