public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107967] [13 regression] The gcc commit 2f7f9edd28d caused the glibc make check fails.
Date: Mon, 05 Dec 2022 09:56:19 +0000 [thread overview]
Message-ID: <bug-107967-4-Z0GT9byRXl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107967-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107967
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |13.0
Summary|The gcc commit 2f7f9edd28d |[13 regression] The gcc
|caused the glibc make check |commit 2f7f9edd28d caused
|fails. |the glibc make check fails.
next prev parent reply other threads:[~2022-12-05 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 2:51 [Bug c/107967] New: " caiyinyu at loongson dot cn
2022-12-05 8:24 ` [Bug tree-optimization/107967] " rguenth at gcc dot gnu.org
2022-12-05 9:08 ` caiyinyu at loongson dot cn
2022-12-05 9:56 ` pinskia at gcc dot gnu.org [this message]
2022-12-05 10:35 ` [Bug tree-optimization/107967] [13 regression] The gcc commit r13-3923 " jakub at gcc dot gnu.org
2022-12-05 10:55 ` aldyh at gcc dot gnu.org
2022-12-05 14:29 ` marxin at gcc dot gnu.org
2022-12-05 16:40 ` jakub at gcc dot gnu.org
2022-12-06 1:32 ` caiyinyu at loongson dot cn
2022-12-06 15:59 ` jakub at gcc dot gnu.org
2022-12-06 17:16 ` jakub at gcc dot gnu.org
2022-12-06 20:06 ` jakub at gcc dot gnu.org
2022-12-07 1:34 ` caiyinyu at loongson dot cn
2022-12-07 16:59 ` amacleod at redhat dot com
2022-12-08 9:36 ` cvs-commit at gcc dot gnu.org
2022-12-08 10:24 ` jakub at gcc dot gnu.org
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=bug-107967-4-Z0GT9byRXl@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).