From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Richard Guenther <rguenther@suse.de>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
Dave Korn <dave.korn.cygwin@googlemail.com>,
gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Wed, 30 Sep 2009 15:00:00 -0000 [thread overview]
Message-ID: <20090930134830.GA4673@bromo.med.uc.edu> (raw)
In-Reply-To: <alpine.LNX.2.00.0909301047130.4520@zhemvz.fhfr.qr>
On Wed, Sep 30, 2009 at 10:49:40AM +0200, Richard Guenther wrote:
> >
> > Now, submitting a one liner as your first attempt@a new pass today
> > and then claiming the rest are just fixes, would be a stretch :-), but
> > for a patch like yours it does not seem unreasonable.
>
> Just to followup once and answer all the multiple requests that have
> been (and will be) come up - during stage 3 it is up to the respective
> maintainers to decide what is considered a bugfix and whether to allow
> changes to go in that were submitted during stage 1. The release
> managers trust the maintainers to make stage 3 a success - which means
> mainly fixing fallout from stage 1 or to complete features that have
> been checked in during stage 1.
>
> Thanks,
> Richard.
>
Richard,
Is it safe to assume that with the LTO patches currently
unreviewed, the Oct. 1st deadline for stage 1 will be pushed
back? I ask because Iain is still working on the final patch
to solve PR39888 for darwin. If we in fact miss the transition
to stage 1, can this patch still go into gcc 4.5 since it is
target specific? Allowing it in would have the advantage of
setting the stage for reinstalling...
http://gcc.gnu.org/ml/gcc-patches/2008-12/msg01259.html
into gcc 4.5 without breaking darwin (since we could
just default on -muse-shared-libgcc-ext for that platform).
Thanks in advance for any clarifications as I am really
hoping some form of...
http://gcc.gnu.org/bugzilla/attachment.cgi?id=18657
can make it into gcc 4.5.
Jack
next prev parent reply other threads:[~2009-09-30 13:48 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
2009-09-29 22:59 ` Gerald Pfeifer
2009-09-30 10:40 ` Richard Guenther
2009-09-30 15:00 ` Jack Howarth [this message]
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=20090930134830.GA4673@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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).