From: "H.J. Lu" <hjl.tools@gmail.com>
To: Richard Biener <rguenther@suse.de>, Uros Bizjak <ubizjak@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: GCC 11.1.1 Status Report (2021-07-06)
Date: Thu, 15 Jul 2021 05:35:05 -0700 [thread overview]
Message-ID: <CAMe9rOotLq8HZi779tfZCnBNXa7aT85LiWkdiMnjwJqrtSCs_w@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2107060900070.10711@zhemvz.fhfr.qr>
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.
next prev parent reply other threads:[~2021-07-15 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 7:00 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 [this message]
2021-07-15 12:38 ` Richard Biener
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=CAMe9rOotLq8HZi779tfZCnBNXa7aT85LiWkdiMnjwJqrtSCs_w@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=ubizjak@gmail.com \
/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).