public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/sphinx] testsuite: Add -Wno-psabi to pr94920 tests [PR94920] Date: Thu, 28 Jul 2022 12:10:38 +0000 (GMT) [thread overview] Message-ID: <20220728121038.6EDDA3856DF1@sourceware.org> (raw) https://gcc.gnu.org/g:f0400e2a86888c08bbdba511f9abd2d4e7ba8e9e commit f0400e2a86888c08bbdba511f9abd2d4e7ba8e9e Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Jul 27 12:02:12 2022 +0200 testsuite: Add -Wno-psabi to pr94920 tests [PR94920] These tests fail on ia32, because we get -Wpsabi warnings. Fixed by adding -Wno-psabi. The pr94920.C test still fails the ABS_EXPR scan-tree-dump though, I think we'll need to add vect options and use vect_int effective target or something similar. 2022-07-27 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/94920 * g++.dg/pr94920.C: Add -Wno-psabi to dg-options. * g++.dg/pr94920-1.C: Add dg-additional-options -Wno-psabi. Diff: --- gcc/testsuite/g++.dg/pr94920-1.C | 1 + gcc/testsuite/g++.dg/pr94920.C | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.dg/pr94920-1.C b/gcc/testsuite/g++.dg/pr94920-1.C index 6c6483eab2d..f8fa14a537a 100644 --- a/gcc/testsuite/g++.dg/pr94920-1.C +++ b/gcc/testsuite/g++.dg/pr94920-1.C @@ -1,4 +1,5 @@ /* PR tree-optimization/94920 */ +/* { dg-additional-options "-Wno-psabi" } */ /* { dg-do run } */ #include "pr94920.C" diff --git a/gcc/testsuite/g++.dg/pr94920.C b/gcc/testsuite/g++.dg/pr94920.C index 925ec4f42f1..126b00478d2 100644 --- a/gcc/testsuite/g++.dg/pr94920.C +++ b/gcc/testsuite/g++.dg/pr94920.C @@ -1,6 +1,6 @@ /* PR tree-optimization/94920 */ /* { dg-do compile } */ -/* { dg-options "-O2 -fdump-tree-optimized" } */ +/* { dg-options "-O2 -Wno-psabi -fdump-tree-optimized" } */ typedef int __attribute__((vector_size(4*sizeof(int)))) vint;
reply other threads:[~2022-07-28 12:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220728121038.6EDDA3856DF1@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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).