public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105147] New test case gcc.dg/pr105140.c introduced in r12-7979-geaaf77dd85c333 has excess errors Date: Tue, 05 Apr 2022 06:04:39 +0000 [thread overview] Message-ID: <bug-105147-4-UGt0XkCsfQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105147-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105147 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING Component|testsuite |target Keywords| |rejects-valid Last reconfirmed| |2022-04-05 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Why is this promoted to an error? Note the mismatch between void bar (); bar (int i, int j, int k, V v) { } is required to trigger the ICE and the testcase passes -w -Wno-psabi If you think the target is right in rejecting this please add a /* { dg-skip-if "" { <... proper target for altivec ...> } } */
next prev parent reply other threads:[~2022-04-05 6:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-04 16:35 [Bug testsuite/105147] New: " seurer at gcc dot gnu.org 2022-04-05 6:04 ` rguenth at gcc dot gnu.org [this message] 2022-04-05 15:14 ` [Bug target/105147] " segher at gcc dot gnu.org 2022-04-06 5:57 ` rguenther at suse dot de 2022-04-06 15:36 ` cvs-commit at gcc dot gnu.org 2022-04-06 15:38 ` segher at gcc dot gnu.org 2022-04-07 5:35 ` cvs-commit at gcc dot gnu.org 2022-05-25 6:14 ` cvs-commit at gcc dot gnu.org 2022-05-25 6:14 ` cvs-commit at gcc dot gnu.org 2022-05-25 6:15 ` rguenth at gcc dot gnu.org 2022-05-27 13:15 ` cvs-commit at gcc dot gnu.org 2022-05-27 13:15 ` 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-105147-4-UGt0XkCsfQ@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).