This is the mail archive of the
mailing list for the GCC project.
Re: GCC 4.3.0 Status Report (2007-09-04)
- From: "Ramana Radhakrishnan" <ramana dot r at gmail dot com>
- To: "Mark Mitchell" <mark at codesourcery dot com>
- Cc: GCC <gcc at gcc dot gnu dot org>, ramana dot radhakrishnan at celunite dot com
- Date: Wed, 12 Sep 2007 17:55:54 +0530
- Subject: Re: GCC 4.3.0 Status Report (2007-09-04)
- References: <46DE1713.firstname.lastname@example.org>
I apologize for the late response to your mail but I sort of did these
patches up recently .
I have a couple of patches that I submitted / intend to submit . One
of them was submitted today regarding a small improvement to the
auto-increment pass. I am not sure if this is suitable for stage3 if
it is approved.
The other patch that we have for submission is relatively trivial and
tries to be more precise with size costs for builtins while inlining.
I guess that should be alright for stage3 .
> We are closing in on Stage 3, previously announced for September 10th.
> At this point, I'm not aware of any reason to delay that date. Are
> there any Stage 2 patches that people don't think will be submitted by
> that point?
> Are there Stage 1 or Stage 2 patches in need of review? I'll do my best
> to either (a) convince someone to review them, or (b) review them myself.
> Priority #
> -------- ---
> P1 43
> P2 118
> P3 4
> Total 165
> Obviously, that's rather more P1s than we'd like. As I mentioned in my
> previous status report, of particular concern is that we've got a lot of
> 4.3-only P1s. I'm sure many of those won't be too hard to fix, but we
> still need to go and fix them.
> I'm concerned about getting into a situation where we say "well, 4.2 has
> some bugs, but all of those are fixed in 4.3" and then realize that "oh,
> well, 4.3 has different bugs too, but those are all fixed in 4.4" and so
> Previous Report
> Mark Mitchell
> (650) 331-3385 x713