public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* GCC 11.1.1 Status Report (2021-07-06)
@ 2021-07-06  7:00 Richard Biener
  2021-07-14 14:03 ` H.J. Lu
  2021-07-15 12:35 ` H.J. Lu
  0 siblings, 2 replies; 5+ messages in thread
From: Richard Biener @ 2021-07-06  7:00 UTC (permalink / raw)
  To: gcc; +Cc: gcc-patches


Status
======

The GCC 11 branch is open for regression and documentation fixes.
It's time for a GCC 11.2 release and we are aiming for a release
candidate in about two weeks which would result in the GCC 11.2
release about three months after GCC 11.1.

Two weeks give you ample time to care for important regressions
and backporting of fixes.  Please also look out for issues on
non-primary/secondary targets.


Quality Data
============

Priority          #   Change from last report
--------        ---   -----------------------
P1              
P2              272   +  20
P3               94   +  56 
P4              210   +   2
P5               24   -   1
--------        ---   -----------------------
Total P1-P3     366   +  76
Total		600   +  79


Previous Report
===============

https://gcc.gnu.org/pipermail/gcc/2021-April/235923.html

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: GCC 11.1.1 Status Report (2021-07-06)
  2021-07-06  7:00 GCC 11.1.1 Status Report (2021-07-06) Richard Biener
@ 2021-07-14 14:03 ` H.J. Lu
  2021-07-15  5:55   ` Richard Biener
  2021-07-15 12:35 ` H.J. Lu
  1 sibling, 1 reply; 5+ messages in thread
From: H.J. Lu @ 2021-07-14 14:03 UTC (permalink / raw)
  To: Richard Biener, Uros Bizjak; +Cc: GCC Development, GCC Patches

On Tue, Jul 6, 2021 at 12:00 AM Richard Biener <rguenther@suse.de> wrote:
>
>
> Status
> ======
>
> The GCC 11 branch is open for regression and documentation fixes.
> It's time for a GCC 11.2 release and we are aiming for a release
> candidate in about two weeks which would result in the GCC 11.2
> release about three months after GCC 11.1.
>
> Two weeks give you ample time to care for important regressions
> and backporting of fixes.  Please also look out for issues on
> non-primary/secondary targets.
>
>
> Quality Data
> ============
>
> Priority          #   Change from last report
> --------        ---   -----------------------
> P1
> P2              272   +  20
> P3               94   +  56
> P4              210   +   2
> P5               24   -   1
> --------        ---   -----------------------
> Total P1-P3     366   +  76
> Total           600   +  79
>
>
> Previous Report
> ===============
>
> https://gcc.gnu.org/pipermail/gcc/2021-April/235923.html

Hi,

I'd like to backport this regression fix:

https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=cc11b924bfe7752edbba052ca71653f46a60887a

to GCC 11 for

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101395

Thanks.

-- 
H.J.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: GCC 11.1.1 Status Report (2021-07-06)
  2021-07-14 14:03 ` H.J. Lu
@ 2021-07-15  5:55   ` Richard Biener
  0 siblings, 0 replies; 5+ messages in thread
From: Richard Biener @ 2021-07-15  5:55 UTC (permalink / raw)
  To: H.J. Lu; +Cc: Uros Bizjak, GCC Development, GCC Patches

On Wed, 14 Jul 2021, H.J. Lu wrote:

> On Tue, Jul 6, 2021 at 12:00 AM Richard Biener <rguenther@suse.de> wrote:
> >
> >
> > Status
> > ======
> >
> > The GCC 11 branch is open for regression and documentation fixes.
> > It's time for a GCC 11.2 release and we are aiming for a release
> > candidate in about two weeks which would result in the GCC 11.2
> > release about three months after GCC 11.1.
> >
> > Two weeks give you ample time to care for important regressions
> > and backporting of fixes.  Please also look out for issues on
> > non-primary/secondary targets.
> >
> >
> > Quality Data
> > ============
> >
> > Priority          #   Change from last report
> > --------        ---   -----------------------
> > P1
> > P2              272   +  20
> > P3               94   +  56
> > P4              210   +   2
> > P5               24   -   1
> > --------        ---   -----------------------
> > Total P1-P3     366   +  76
> > Total           600   +  79
> >
> >
> > Previous Report
> > ===============
> >
> > https://gcc.gnu.org/pipermail/gcc/2021-April/235923.html
> 
> Hi,
> 
> I'd like to backport this regression fix:
> 
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=cc11b924bfe7752edbba052ca71653f46a60887a
> 
> to GCC 11 for
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101395

OK.

Richard.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: GCC 11.1.1 Status Report (2021-07-06)
  2021-07-06  7:00 GCC 11.1.1 Status Report (2021-07-06) Richard Biener
  2021-07-14 14:03 ` H.J. Lu
@ 2021-07-15 12:35 ` H.J. Lu
  2021-07-15 12:38   ` Richard Biener
  1 sibling, 1 reply; 5+ messages in thread
From: H.J. Lu @ 2021-07-15 12:35 UTC (permalink / raw)
  To: Richard Biener, Uros Bizjak; +Cc: GCC Development, GCC Patches

On Tue, Jul 6, 2021 at 12:00 AM Richard Biener <rguenther@suse.de> wrote:
>
>
> Status
> ======
>
> The GCC 11 branch is open for regression and documentation fixes.
> It's time for a GCC 11.2 release and we are aiming for a release
> candidate in about two weeks which would result in the GCC 11.2
> release about three months after GCC 11.1.
>
> Two weeks give you ample time to care for important regressions
> and backporting of fixes.  Please also look out for issues on
> non-primary/secondary targets.
>
>
> Quality Data
> ============
>
> Priority          #   Change from last report
> --------        ---   -----------------------
> P1
> P2              272   +  20
> P3               94   +  56
> P4              210   +   2
> P5               24   -   1
> --------        ---   -----------------------
> Total P1-P3     366   +  76
> Total           600   +  79
>
>
> Previous Report
> ===============
>
> https://gcc.gnu.org/pipermail/gcc/2021-April/235923.html

I'd like to backport:

https://gcc.gnu.org/g:3f04e3782536ad2f9cfbb8cfe6630e9f9dd8af4c

to fix this GCC 11 regression:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101023

-- 
H.J.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: GCC 11.1.1 Status Report (2021-07-06)
  2021-07-15 12:35 ` H.J. Lu
@ 2021-07-15 12:38   ` Richard Biener
  0 siblings, 0 replies; 5+ messages in thread
From: Richard Biener @ 2021-07-15 12:38 UTC (permalink / raw)
  To: H.J. Lu; +Cc: Uros Bizjak, GCC Development, GCC Patches

On Thu, 15 Jul 2021, H.J. Lu wrote:

> On Tue, Jul 6, 2021 at 12:00 AM Richard Biener <rguenther@suse.de> wrote:
> >
> >
> > Status
> > ======
> >
> > The GCC 11 branch is open for regression and documentation fixes.
> > It's time for a GCC 11.2 release and we are aiming for a release
> > candidate in about two weeks which would result in the GCC 11.2
> > release about three months after GCC 11.1.
> >
> > Two weeks give you ample time to care for important regressions
> > and backporting of fixes.  Please also look out for issues on
> > non-primary/secondary targets.
> >
> >
> > Quality Data
> > ============
> >
> > Priority          #   Change from last report
> > --------        ---   -----------------------
> > P1
> > P2              272   +  20
> > P3               94   +  56
> > P4              210   +   2
> > P5               24   -   1
> > --------        ---   -----------------------
> > Total P1-P3     366   +  76
> > Total           600   +  79
> >
> >
> > Previous Report
> > ===============
> >
> > https://gcc.gnu.org/pipermail/gcc/2021-April/235923.html
> 
> I'd like to backport:
> 
> https://gcc.gnu.org/g:3f04e3782536ad2f9cfbb8cfe6630e9f9dd8af4c
> 
> to fix this GCC 11 regression:
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101023

OK.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-07-15 12:38 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-06  7:00 GCC 11.1.1 Status Report (2021-07-06) Richard Biener
2021-07-14 14:03 ` H.J. Lu
2021-07-15  5:55   ` Richard Biener
2021-07-15 12:35 ` H.J. Lu
2021-07-15 12:38   ` Richard Biener

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).