From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Tue, 29 Sep 2009 22:08:00 -0000 [thread overview]
Message-ID: <4AC27D21.6020905@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0909192244530.4520@zhemvz.fhfr.qr>
Richard Guenther wrote:
> Status
> ======
>
> The trunk is in Stage 1. Stage 1 will end on Sep 30th.
Richard, I've got a patch for adding what I think (but may be wrong) counts
as a new feature - shared library libstdc++ as DLLs on windows platforms - and
it's been stuck in review limbo for two and a half months now, during which
time I have been repeatedly updating it, retesting it, and even fixed a couple
of minor bugs that cropped up in that time:
refs: The original series of patches at
[0/4] http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01042.html
[1/4] http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01044.html
[2/4] http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01046.html
[3/4] http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01047.html
[4/4] http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01048.html
and the various tweaked and updated respins at
http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01631.html
http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00877.html
http://gcc.gnu.org/ml/gcc-patches/2009-08/msg01570.html
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00209.html
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg00500.html
http://gcc.gnu.org/ml/gcc-patches/2009-09/msg01963.html
and test results at
http://gcc.gnu.org/ml/gcc-testresults/2009-07/msg01813.html
http://gcc.gnu.org/ml/gcc-testresults/2009-07/msg01814.html
http://gcc.gnu.org/ml/gcc-testresults/2009-08/msg03258.html
http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg00291.html
http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg00292.html
http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg00644.html
http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg01450.html
We have ~48 hours left for stage 1 and I can't be confident of getting it
reviewed in the remaining time, so I'd like to make a special request: can
you, as RM, please say that this is OK in principle and that if I can get v3
approval (it already has all other necessary approvals) I can check it in
during stage 3 before we branch?
cheers,
DaveK
next prev parent reply other threads:[~2009-09-29 21:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 20:57 Richard Guenther
2009-09-19 22:03 ` Steven Bosscher
2009-09-19 22:22 ` Richard Guenther
2009-09-20 1:21 ` Geert Bosch
2009-09-20 1:00 ` Jack Howarth
2009-09-20 1:35 ` Dave Korn
2009-09-20 8:54 ` Richard Guenther
2009-09-20 11:38 ` Dave Korn
2009-09-20 11:48 ` Richard Guenther
2009-09-20 11:53 ` Dave Korn
2009-09-24 14:44 ` Jason Merrill
2009-09-24 14:50 ` Richard Guenther
2009-09-21 18:23 ` Cary Coutant
2009-09-21 18:57 ` Jack Howarth
2009-09-21 21:05 ` Cary Coutant
2009-09-21 21:10 ` Cary Coutant
2009-09-29 18:10 ` Sriraman Tallam
2009-09-29 22:08 ` Dave Korn [this message]
2009-09-29 22:59 ` Gerald Pfeifer
2009-09-30 10:40 ` Richard Guenther
2009-09-30 15:00 ` Jack Howarth
2009-10-01 0:17 ` Neil Vachharajani
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=4AC27D21.6020905@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).