From: Sriraman Tallam <tmsriram@google.com>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org, Diego Novillo <dnovillo@google.com>,
Ian Lance Taylor <iant@google.com>
Subject: Re: GCC 4.5 Status Report (2009-09-19)
Date: Tue, 29 Sep 2009 18:10:00 -0000 [thread overview]
Message-ID: <863b0cbf0909291052h48f7a957v5906fffcecb87e9d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0909192244530.4520@zhemvz.fhfr.qr>
Hi,
I have a zero-extension elimination patch that has been reviewed and needs
one minor fix before it is ready for submission. I can get this in by Thursday,
October 1st. Would it be alright to submit this patch then ?
Thanks,
-Sriraman.
On Sat, Sep 19, 2009 at 1:57 PM, Richard Guenther <rguenther@suse.de> wrote:
>
> Status
> ======
>
> The trunk is in Stage 1. Stage 1 will end on Sep 30th. After Stage 1
> Stage 3 follows with only bugfixes and no new features allowed.
> Stage 3 will end Nov 30th.
>
> Since the last status report we have merged the VTA branch and pieces
> of the LTO branch. The named address-spaces changes are still pending
> review but I expect it to be merged before the end of Stage 1.
> The rest of the LTO branch will be merged last, which practically
> means after Stage 1 is over. Thus, starting Oct 1st the trunk will
> be frozen for the LTO merge and I'll announce Stage 3 once the merge
> is completed.
>
> There are still new ports pending review and approval. As usual
> new ports can be accepted also during Stage 3.
>
> We've been accumulating quite a number of P1 bugs. Entering Stage 3
> should allow to improve considerably here in a short time.
>
> Quality Data
> ============
>
> Priority # Change from Last Report
> -------- --- -----------------------
> P1 22 + 6
> P2 111 + 7
> P3 6 + 6
> -------- --- -----------------------
> Total 139 +19
>
> Previous Report
> ===============
>
> http://gcc.gnu.org/ml/gcc/2009-08/msg00427.html
>
> The next report will be sent by me announcing Stage 3 begin.
>
> --
> Richard Guenther <rguenther@suse.de>
> Novell / SUSE Labs
> SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex
>
next prev parent reply other threads:[~2009-09-29 17:53 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 [this message]
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
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=863b0cbf0909291052h48f7a957v5906fffcecb87e9d@mail.gmail.com \
--to=tmsriram@google.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--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).