public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Mon, 18 Apr 2022 02:36:47 +0000 [thread overview] Message-ID: <bug-105266-4-XSEvF9J9Xe@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 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:021b51814d67bedd8f41ac07edfd05654140c6e5 commit r12-8184-g021b51814d67bedd8f41ac07edfd05654140c6e5 Author: Kewen Lin <linkw@linux.ibm.com> Date: Sun Apr 17 21:34:51 2022 -0500 testsuite: Skip pr105250.c for powerpc and s390 [PR105266] This test case pr105250.c is like its related pr105140.c, which suffers the error with message like "{AltiVec,vector} argument passed to unprototyped" on powerpc and s390. So like commits r12-8025 and r12-8039, this fix is to add the dg-skip-if for powerpc*-*-* and s390*-*-*. gcc/testsuite/ChangeLog: PR testsuite/105266 * gcc.dg/pr105250.c: Skip for powerpc*-*-* and s390*-*-*.
next prev parent reply other threads:[~2022-04-18 2:36 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 ` [Bug testsuite/105266] new test case gcc.dg/pr105250.c fails with excess errors " linkw at gcc dot gnu.org 2022-04-14 3:16 ` 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 [this message] 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-XSEvF9J9Xe@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).