* GCC 4.3.3 Status Report (2009-01-17), branch frozen for release
@ 2009-01-16 23:03 Richard Guenther
2009-01-16 23:08 ` H.J. Lu
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Richard Guenther @ 2009-01-16 23:03 UTC (permalink / raw)
To: gcc; +Cc: gcc-patches, fortran, libstdc++, java
It's not my turn to send a status report, but as I plan doing a release
candidate for GCC 4.3.3 soon I thought a status report for that would
be in order.
Status
======
The GCC 4.3 branch is now frozen in preparation for a release candidate
for the GCC 4.3.3 release. When the branch is unfrozen again I will
send a message stating so. All checkins to the branch require approval
by a release manager now.
There is a single regression that shows up as P1, but as it is not
a regression on the branch (but from the tree-ssa merge) it does not
block the GCC 4.3.3 release (but the bug priority is considered the priority
for the newest release the bug is a regression for).
I am not aware of any issues blocking an immediate release of GCC 4.3.3.
Please make me aware of such issues by replying to this mail and/or
by CCing me on bugzillas that are regressions on the GCC 4.3 branch
but are not marked as such (a regression on the GCC 4.3 branch is a
bug with a testcase that worked in a previous GCC 4.3 based release
but fails on the top of the GCC 4.3 branch).
Quality Data
============
Priority # Change from Last Report
-------- --- -----------------------
P1 1 - 4
P2 137 + 7
P3 2 - 1
-------- --- -----------------------
Total 140 + 2
The next status report will be sent by me.
Richard.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: GCC 4.3.3 Status Report (2009-01-17), branch frozen for release
2009-01-16 23:03 GCC 4.3.3 Status Report (2009-01-17), branch frozen for release Richard Guenther
@ 2009-01-16 23:08 ` H.J. Lu
2009-01-17 8:33 ` Paul Richard Thomas
2009-01-17 18:29 ` John David Anglin
2 siblings, 0 replies; 5+ messages in thread
From: H.J. Lu @ 2009-01-16 23:08 UTC (permalink / raw)
To: Richard Guenther; +Cc: gcc, gcc-patches, fortran, libstdc++, java
On Fri, Jan 16, 2009 at 3:03 PM, Richard Guenther <rguenther@suse.de> wrote:
>
> It's not my turn to send a status report, but as I plan doing a release
> candidate for GCC 4.3.3 soon I thought a status report for that would
> be in order.
>
> Status
> ======
>
> The GCC 4.3 branch is now frozen in preparation for a release candidate
> for the GCC 4.3.3 release. When the branch is unfrozen again I will
> send a message stating so. All checkins to the branch require approval
> by a release manager now.
>
> There is a single regression that shows up as P1, but as it is not
> a regression on the branch (but from the tree-ssa merge) it does not
> block the GCC 4.3.3 release (but the bug priority is considered the priority
> for the newest release the bug is a regression for).
>
> I am not aware of any issues blocking an immediate release of GCC 4.3.3.
> Please make me aware of such issues by replying to this mail and/or
> by CCing me on bugzillas that are regressions on the GCC 4.3 branch
> but are not marked as such (a regression on the GCC 4.3 branch is a
> bug with a testcase that worked in a previous GCC 4.3 based release
> but fails on the top of the GCC 4.3 branch).
>
I think
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38877
also happens on 4.3 branch.
--
H.J.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: GCC 4.3.3 Status Report (2009-01-17), branch frozen for release
2009-01-16 23:03 GCC 4.3.3 Status Report (2009-01-17), branch frozen for release Richard Guenther
2009-01-16 23:08 ` H.J. Lu
@ 2009-01-17 8:33 ` Paul Richard Thomas
2009-01-17 9:45 ` Paul Richard Thomas
2009-01-17 18:29 ` John David Anglin
2 siblings, 1 reply; 5+ messages in thread
From: Paul Richard Thomas @ 2009-01-17 8:33 UTC (permalink / raw)
To: Richard Guenther; +Cc: gcc, gcc-patches, fortran, libstdc++, java
Richard,
I would like to revert the cause of the regression reported yesterday
in http://gcc.gnu.org/ml/fortran/2009-01/msg00197.html - I'll do it in
the next hour, if that is alright?
Cheers
Paul
On Sat, Jan 17, 2009 at 12:03 AM, Richard Guenther <rguenther@suse.de> wrote:
>
> It's not my turn to send a status report, but as I plan doing a release
> candidate for GCC 4.3.3 soon I thought a status report for that would
> be in order.
>
> Status
> ======
>
> The GCC 4.3 branch is now frozen in preparation for a release candidate
> for the GCC 4.3.3 release. When the branch is unfrozen again I will
> send a message stating so. All checkins to the branch require approval
> by a release manager now.
>
> There is a single regression that shows up as P1, but as it is not
> a regression on the branch (but from the tree-ssa merge) it does not
> block the GCC 4.3.3 release (but the bug priority is considered the priority
> for the newest release the bug is a regression for).
>
> I am not aware of any issues blocking an immediate release of GCC 4.3.3.
> Please make me aware of such issues by replying to this mail and/or
> by CCing me on bugzillas that are regressions on the GCC 4.3 branch
> but are not marked as such (a regression on the GCC 4.3 branch is a
> bug with a testcase that worked in a previous GCC 4.3 based release
> but fails on the top of the GCC 4.3 branch).
>
>
> Quality Data
> ============
>
> Priority # Change from Last Report
> -------- --- -----------------------
> P1 1 - 4
> P2 137 + 7
> P3 2 - 1
> -------- --- -----------------------
> Total 140 + 2
>
>
> The next status report will be sent by me.
>
> Richard.
>
--
The knack of flying is learning how to throw yourself at the ground and miss.
--Hitchhikers Guide to the Galaxy
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: GCC 4.3.3 Status Report (2009-01-17), branch frozen for release
2009-01-17 8:33 ` Paul Richard Thomas
@ 2009-01-17 9:45 ` Paul Richard Thomas
0 siblings, 0 replies; 5+ messages in thread
From: Paul Richard Thomas @ 2009-01-17 9:45 UTC (permalink / raw)
To: Richard Guenther; +Cc: gcc, gcc-patches, fortran, libstdc++, java
> Richard,
>
> I would like to revert the cause of the regression reported yesterday
> in http://gcc.gnu.org/ml/fortran/2009-01/msg00197.html - I'll do it in
> the next hour, if that is alright?
>
> Cheers
>
> Paul
Duly reverted on trunk and 4.3.
Paul
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: GCC 4.3.3 Status Report (2009-01-17), branch frozen for release
2009-01-16 23:03 GCC 4.3.3 Status Report (2009-01-17), branch frozen for release Richard Guenther
2009-01-16 23:08 ` H.J. Lu
2009-01-17 8:33 ` Paul Richard Thomas
@ 2009-01-17 18:29 ` John David Anglin
2 siblings, 0 replies; 5+ messages in thread
From: John David Anglin @ 2009-01-17 18:29 UTC (permalink / raw)
To: Richard Guenther; +Cc: gcc, gcc-patches, fortran, libstdc++, java
On Sat, 17 Jan 2009, Richard Guenther wrote:
> It's not my turn to send a status report, but as I plan doing a release
> candidate for GCC 4.3.3 soon I thought a status report for that would
> be in order.
Sorry Richard, I didn't see this until too late. I committed three
PA changes this morning, the first being fairly important.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-01-17 18:29 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-01-16 23:03 GCC 4.3.3 Status Report (2009-01-17), branch frozen for release Richard Guenther
2009-01-16 23:08 ` H.J. Lu
2009-01-17 8:33 ` Paul Richard Thomas
2009-01-17 9:45 ` Paul Richard Thomas
2009-01-17 18:29 ` John David Anglin
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).