public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/105266] new test case gcc.dg/pr105250.c fails with excess errors in r12-8134-g4e892de6774f86 Date: Thu, 14 Apr 2022 02:27:40 +0000 [thread overview] Message-ID: <bug-105266-4-aP64fr0e6D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105266-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105266 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linkw at gcc dot gnu.org --- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> --- This is like PR105147, we need dg-skip for powerpc and s390 like what we did in PR105147, the fix could be like: /* { dg-skip-if "PR105266" { powerpc*-*-* s390*-*-* } } */
next prev parent reply other threads:[~2022-04-14 2:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 20:41 [Bug testsuite/105266] New: new test case gcc.dg/pr105250.c fails " seurer at gcc dot gnu.org 2022-04-14 2:27 ` linkw at gcc dot gnu.org [this message] 2022-04-14 3:16 ` [Bug testsuite/105266] new test case gcc.dg/pr105250.c fails with excess errors " linkw at gcc dot gnu.org 2022-04-14 6:24 ` rguenth at gcc dot gnu.org 2022-04-18 2:36 ` cvs-commit at gcc dot gnu.org 2022-04-18 2:38 ` linkw at gcc dot gnu.org 2022-05-25 14:34 ` seurer at gcc dot gnu.org 2022-05-27 5:59 ` cvs-commit at gcc dot gnu.org 2022-05-27 5:59 ` rguenth at gcc dot gnu.org 2022-05-27 13:16 ` 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-105266-4-aP64fr0e6D@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).