public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guihaoc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100952] [12/13 regression] several test case failures after r12-1202
Date: Tue, 20 Dec 2022 03:02:05 +0000 [thread overview]
Message-ID: <bug-100952-4-P0JczZdWqo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100952-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100952
HaoChen Gui <guihaoc at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #19 from HaoChen Gui <guihaoc at gcc dot gnu.org> ---
Closing as fixed then (pr56605.c still fails on older branches, but that is
harmless). Other issues are all fixed.
prev parent reply other threads:[~2022-12-20 3:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 20:21 [Bug target/100952] New: [12 " seurer at gcc dot gnu.org
2021-06-08 0:40 ` [Bug target/100952] " seurer at gcc dot gnu.org
2021-06-08 5:14 ` guihaoc at gcc dot gnu.org
2021-06-08 6:09 ` guihaoc at gcc dot gnu.org
2021-06-08 7:02 ` guihaoc at gcc dot gnu.org
2021-06-08 7:53 ` rguenth at gcc dot gnu.org
2021-06-24 20:39 ` seurer at gcc dot gnu.org
2021-06-25 6:11 ` guihaoc at gcc dot gnu.org
2021-06-25 6:12 ` guihaoc at gcc dot gnu.org
2021-06-25 17:59 ` seurer at gcc dot gnu.org
2021-07-23 2:01 ` cvs-commit at gcc dot gnu.org
2021-07-29 7:07 ` cvs-commit at gcc dot gnu.org
2021-08-02 3:14 ` cvs-commit at gcc dot gnu.org
2021-08-30 10:06 ` cvs-commit at gcc dot gnu.org
2021-12-20 6:37 ` guihaoc at gcc dot gnu.org
2022-01-14 18:37 ` wschmidt at gcc dot gnu.org
2022-01-14 18:48 ` seurer at gcc dot gnu.org
2022-01-17 5:55 ` guihaoc at gcc dot gnu.org
2022-05-06 8:30 ` [Bug target/100952] [12/13 " jakub at gcc dot gnu.org
2022-07-26 13:32 ` rguenth at gcc dot gnu.org
2022-12-20 3:02 ` guihaoc at gcc dot gnu.org [this message]
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-100952-4-P0JczZdWqo@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).