From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: GCC 3.0 Status Report
Date: Mon, 19 Mar 2001 12:23:00 -0000 [thread overview]
Message-ID: <20010319122804S.mitchell@codesourcery.com> (raw)
I was flaky with the weekly status report over the last couple of
weeks, but I'm trying to turn over a new leaf.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
GCC 3.0 Status Report
=====================
Overall
-------
The Steering Committee has concluded that the release criteria
are somewhat over-ambitious given the lack of resources available
to complete some of the tasks.
Therefore, the GCC 3.0 release will be largely a functionality
release, featuring the rewritten x86 back-end, improved Java
compiler, new C++ ABI, and new C++ standard library. Stability
will remain a focus, but quality of the generated code will
become a secondary priority. This withstanding, we believe that
GCC 3.0 will generate better code than GCC 2.95.x in many
circumstances.
In the short term, we will focus on compile-time performance,
especially in C++. At that point, application testing will
become the major focus. Performance of the generated code
will be a greater focus of the 3.1 release.
Last Week
---------
Analysis of open bugs is largely complete. Many of the remainder
are hard to analyze due to being target-specific in various ways.
Richard Henderson provided a number of DWARF2 fixes and
improvements. Zack Weinberg checked in a number of cleanups
to simply configuration.
I began working on a variety of compile-time performance
optimizations. One of the lowest-hanging pieces of fruit appears
to be lazy name-mangling in C++. I've got that working and will
check it in soon. Preliminary work on this project broke the ARM
bootstrap. This turned out to be a generic optimization bug; it
is now fixed.
Numerous other bugs fixed.
Kudos
-----
For his continuing work on the GCC 3.0 documentation and web-site,
the GCC 3.0 Volunteer of the Week is ...
... Gerald Pfeifer!
Congratulations!
Next Week
---------
Work on compile-time performance.
Fix critical bugs.
next reply other threads:[~2001-03-19 12:23 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 12:23 Mark Mitchell [this message]
2001-03-19 13:35 ` Craig Rodrigues
2001-03-19 16:04 ` Mark Mitchell
2001-03-19 17:16 ` Geoff Keating
2001-03-19 17:26 ` Mark Mitchell
2001-03-19 18:42 ` Stan Shebs
2001-03-19 19:07 ` Daniel Berlin
2001-03-19 19:53 ` Stan Shebs
2001-03-19 20:18 ` Mark Mitchell
2001-03-19 17:43 ` Daniel Berlin
2001-03-19 18:15 ` Geoff Keating
2001-03-19 18:11 ` Daniel Berlin
2001-03-20 4:18 Peter Bienstman
2001-03-27 8:55 Mark Mitchell
2001-03-27 9:51 ` David Edelsohn
2001-04-03 10:38 Mark Mitchell
2001-04-03 13:24 ` Joseph S. Myers
2001-04-03 14:22 ` Toon Moene
2001-04-17 0:32 Mark Mitchell
2001-04-17 16:31 ` Toon Moene
2001-04-17 16:37 ` Mark Mitchell
2001-04-18 7:02 ` Andreas Schwab
2001-04-18 19:51 ` Mark Mitchell
2001-04-19 2:13 ` Gabriel Dos Reis
2001-04-19 8:33 ` Mark Mitchell
2001-04-19 13:36 ` Phil Edwards
2001-04-17 10:32 Michael Elizabeth Chastain
2001-04-17 16:13 John David Anglin
2001-04-17 16:38 ` Gabriel Dos Reis
2001-04-17 18:40 ` John David Anglin
[not found] <no.id>
2001-04-17 19:11 ` John David Anglin
2001-04-18 0:55 ` Mark Mitchell
2001-04-18 9:00 ` John David Anglin
2001-04-18 13:51 ` John David Anglin
2001-04-20 13:36 ` Mark Mitchell
[not found] <1654.987568477@slagheap.cygnus.com>
2001-04-18 10:38 ` John David Anglin
2001-04-18 12:34 Michael Elizabeth Chastain
[not found] <200104182009.NAA09066@bosch.cygnus.com>
2001-04-19 13:07 ` John David Anglin
2001-04-19 13:34 ` Mark Mitchell
2001-04-19 13:39 ` John David Anglin
2001-04-19 15:41 ` Mark Mitchell
2001-04-19 17:43 ` Joe Buck
2001-04-19 17:54 ` Mark Mitchell
2001-04-19 17:30 ` Benjamin Kosnik
2001-04-22 8:41 ` Fergus Henderson
2001-04-19 13:27 Michael Elizabeth Chastain
2001-04-19 13:32 ` John David Anglin
2001-04-19 23:33 Michael Elizabeth Chastain
2001-05-01 17:22 Mark Mitchell
2001-05-01 18:56 Mike Stump
2001-05-02 8:47 ` Mark Mitchell
2001-05-02 16:09 Mike Stump
2001-05-07 9:14 ` Joe Buck
2001-05-14 14:28 Mark Mitchell
2001-05-14 16:44 ` Joseph S. Myers
2001-05-17 9:27 ` Joe Buck
2001-06-11 10:08 ` Joern Rennecke
2001-05-17 2:29 Christian Iseli
2001-05-21 18:48 Mark Mitchell
2001-05-21 20:23 ` Daniel Berlin
2001-05-22 1:44 ` Dennis Bjorklund
2001-05-22 2:33 ` Joseph S. Myers
2001-05-22 7:58 ` Mark Mitchell
2001-05-22 10:52 ` Dennis Bjorklund
2001-05-22 3:37 ` Joseph S. Myers
2001-05-22 3:53 ` Gerald Pfeifer
2001-05-22 13:51 ` Phil Edwards
2001-05-22 14:02 ` Mark Mitchell
2001-05-22 14:22 ` Toon Moene
2001-05-22 14:37 ` Mark Mitchell
2001-06-05 13:23 Mark Mitchell
2001-06-05 13:49 ` Richard Henderson
2001-06-05 14:15 ` Rainer Orth
2001-06-05 18:09 ` Mark Mitchell
2001-06-06 4:54 ` Rainer Orth
2001-06-05 15:16 ` Joseph S. Myers
2001-06-05 15:33 ` benjamin kosnik
2001-06-05 15:56 ` Mark Mitchell
2001-06-05 15:56 ` Franz Sirl
2001-06-05 16:04 ` Mark Mitchell
2001-06-05 21:04 ` Alexandre Petit-Bianco
2001-06-05 23:08 ` Mark Mitchell
2001-06-11 21:48 Mark Mitchell
2001-06-11 22:31 ` Loren James Rittle
2001-06-12 0:56 ` Joseph S. Myers
2001-06-12 1:17 ` Mark Mitchell
2001-06-12 1:57 ` Nathan Sidwell
2001-06-12 9:37 ` Tom Tromey
2001-06-12 3:42 ` Joseph S. Myers
2001-06-12 5:01 ` Franz Sirl
2001-06-12 19:39 ` Stan Shebs
2001-06-13 9:39 ` Mark Mitchell
2001-06-13 11:58 ` Franz Sirl
2001-06-12 5:32 ` Bernd Schmidt
2001-06-12 8:01 ` Geert Bosch
2001-06-12 16:16 ` Roman Zippel
2001-06-12 16:21 ` Mark Mitchell
2001-06-13 5:11 ` Joseph S. Myers
2001-06-13 6:00 ` Gerald Pfeifer
2001-06-13 9:45 ` Mark Mitchell
2001-06-12 17:42 Robert Schweikert
2001-06-12 18:38 ` 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=20010319122804S.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@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).