public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/106120] [13 regression] g++.dg/warn/Wstringop-overflow-4.C fails since r13-1268-g8c99e307b20c50 Date: Fri, 08 Jul 2022 23:10:12 +0000 [thread overview] Message-ID: <bug-106120-4-gti0GI4GeL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106120-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106120 --- Comment #4 from Hans-Peter Nilsson <hp at gcc dot gnu.org> --- The XPASS:es seem to be the same for everyone, with the FAIL only appearing on ILP32. Aldy, how about correcting those xfail markers and adding one for ILP32?
next prev parent reply other threads:[~2022-07-08 23:10 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-28 16:01 [Bug other/106120] New: " seurer at gcc dot gnu.org 2022-06-28 17:25 ` [Bug other/106120] " aldyh at gcc dot gnu.org 2022-06-28 18:14 ` seurer at gcc dot gnu.org 2022-06-29 0:03 ` hp at gcc dot gnu.org 2022-06-29 9:44 ` [Bug testsuite/106120] " rguenth at gcc dot gnu.org 2022-07-08 23:10 ` hp at gcc dot gnu.org [this message] 2022-07-09 6:29 ` aldyh at gcc dot gnu.org 2022-12-14 15:50 ` danglin at gcc dot gnu.org 2022-12-20 14:05 ` rguenth at gcc dot gnu.org 2023-02-10 0:41 ` cvs-commit at gcc dot gnu.org 2023-02-10 18:34 ` hp at gcc dot gnu.org 2023-02-10 18:37 ` seurer at gcc dot gnu.org 2023-02-10 22:52 ` hp at gcc dot gnu.org 2023-11-21 15:21 ` ro at gcc dot gnu.org 2023-11-21 17:54 ` hp at gcc dot gnu.org 2023-11-22 9:09 ` ro at CeBiTec dot Uni-Bielefeld.DE 2023-11-23 0:29 ` cvs-commit 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-106120-4-gti0GI4GeL@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: linkBe 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).