This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.7.0 Status Report (2011-11-08), Stage 1 is over, Stage 3 in effect immediately
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, Walter Lee <walt at tilera dot com>, "Jayant R. Sonar" <Jayant dot Sonar at kpitcummins dot com>, DJ Delorie <dj at redhat dot com>, Douglas B Rupp <rupp at gnat dot com>
- Date: Wed, 9 Nov 2011 17:55:10 +0000 (UTC)
- Subject: Re: GCC 4.7.0 Status Report (2011-11-08), Stage 1 is over, Stage 3 in effect immediately
- References: <20111108112924.GE17997@tyan-ft48-01.lab.bos.redhat.com>
On Tue, 8 Nov 2011, Jakub Jelinek wrote:
> during the last minute, patches submitted during stage1
> may be still accepted, if they don't need significant rewrites,
> but please try to get them in soon. Otherwise only bugfixes
> and documentation fixes are allowed for the trunk.
To be clear since we have several new ports out there: new ports are
generally low-risk if they don't require significant changes to
target-independent code beyond the standard bits such as config.gcc that
are listed in doc/sourcebuild.texi, and can often go in even in stage 4.
I believe we currently have at least the CR16, Tile and RL78 ports
pending, plus the resurrection of the Interix OS port. I believe all four
(or five, since Tile is really two ports) of those ports currently need
the people submitting them to send new versions against current trunk that
address the most recent review comments - and to be pinged as needed until
reviewed. (Take care to ensure they are updated for all the libgcc build
system changes that have gone in recently.)
If maintainers haven't been explicitly proposed to the SC for these ports,
they should be (although a port may sometimes go in without a maintainer
being approved - I think the SC are still considering Epiphany
maintainership - and depending on the author's GCC experience they may not
always be approved as a maintainer initially until they have a reasonable
record of good patches).
--
Joseph S. Myers
joseph@codesourcery.com