From: Gerald Pfeifer <gerald@pfeifer.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Release Status (2003-10-03)
Date: Fri, 03 Oct 2003 22:59:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0310040056511.98273@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <200310032250.h93Moti1003175@doubledemon.codesourcery.com>
On Fri, 3 Oct 2003, Mark Mitchell wrote:
> There are still a lot of open 3.3.2 regressions: 69 at last count,
> which is down from 96 the last time I sent a status report.
> [...]
> There are 150 bugs targeted for GCC 3.4 (up from 143); 46 are C++ bugs
> (up from 44).
Comparing numbers, GCC 3.4 seems in surprisingly good shape (or GCC 3.3
in relatively bad shape). What's your feeling?
Gerald
PS: I applied the patch below to our main page.
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.397
diff -u -3 -p -r1.397 index.html
--- index.html 22 Sep 2003 09:41:01 -0000 1.397
+++ index.html 3 Oct 2003 22:56:39 -0000
@@ -71,7 +71,7 @@ to maintain and improve quality.</p>
<!-- This is a fifth, permanent item. -->
<dt><strong>Release status:</strong>
- <a href="http://gcc.gnu.org/ml/gcc/2003-09/msg00284.html">2003-09-05</a>
+ <a href="http://gcc.gnu.org/ml/gcc/2003-10/msg00119.html">2003-10-03</a>
</dt><dd>
</dd>
next prev parent reply other threads:[~2003-10-03 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 22:51 Mark Mitchell
2003-10-03 22:59 ` Gerald Pfeifer [this message]
2003-10-04 0:23 ` ping, RFA (try 2). DEBUG mainainters: Where to put location_t info? Carlo Wood
2003-10-04 6:19 ` GCC Release Status (2003-10-03) Eric Botcazou
2003-10-04 7:32 ` Gerald Pfeifer
2003-10-04 8:44 ` Jakub Jelinek
2003-10-05 19:52 ` Mark Mitchell
2003-10-05 19:55 ` Mark Mitchell
2003-10-04 2:25 Michael Elizabeth Chastain
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=Pine.BSF.4.58.0310040056511.98273@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.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).