From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: gcc@gcc.gnu.org
Subject: GCC-3.3.3 release status (2003-12-08)
Date: Tue, 09 Dec 2003 11:25:00 -0000 [thread overview]
Message-ID: <m3zne2e33p.fsf@dromion.integrable-solutions.net> (raw)
Hi,
The number of regressions targetted for gcc-3_3-branch is 66. That
number was 68 last week. That appears to be a very slow progress; but
the fact is that it does not capture the reality. Actually, in the
past few days the back-end and middle-end people have been very active
in tracking and fixing at least 13 PRs on the branch (some bug fixes
don't have PR number so I may have missed some). Special thanks
to Roger Sayle, Eric Botcazou, Andrew Pinski and the "bug masters".
The C++ front-end is the winner of the competition 'who has the
highest number of regressions' :-( It seems to have received no much
attention (one regression fix).
I'm still accepting non-regression bug fixes till December 31, but
as we're approaching that date, I'll be more and more stringent. The
idea is that I would not like to see many last minutes patches proposed
for checking on December 31.
Here is a detailed list of existing regressions as targetted for
gcc-3_3-branch. Where I listed individuals, that means bugzilla says
they are assigned the corresponding PR.
* bootstrap: 7817, 13068
* C: 7544, 9209, 11392, 11527(rth)
* C++: 11554, 11697(mmitchel), 11948, 12491, 12507, 12667, 12724,
12779, 12815, 12831, 12862, 13009, 13057, 13070, 13081, 13086,
13173, 13215, 13239, 13262(kriang), 13349
* debug: 6522, 11232, 1365
* inline-asm: 8788
* libgcj: 10353
* libstdc++: 7076(bkoz), 10703, 13351
* middle-end: 10776, 11397
* objc: 7993(shebs)
* optimization: 10392, 11350(rth), 11496, 11841, 12441, 12442,
12576, 12965(ebotcazou), 13031, 13037(sayle), 13060(ebotcazou)
* preprocessor: 13046
* target: 7940, 9201, 9365, 9552, 10692, 10730, 11226, 11271,
11578(kazu), 11587, 11793(aldyh), 11864, 11992, 12158,
12537, 13069
If you think you can help with any PR listed above, then your help is
welcome and appreciated.
Last report: http://gcc.gnu.org/ml/gcc/2003-12/msg00128.html
Next report on December 15, 2003.
Thanks,
-- Gaby
reply other threads:[~2003-12-09 9:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3zne2e33p.fsf@dromion.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--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).