public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Will Schmidt <willschm@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-6795] [PATCH, rs6000] Update pr88233.c test (pr91799) Date: Tue, 19 Jan 2021 17:43:45 +0000 (GMT) [thread overview] Message-ID: <20210119174345.A4C00384A031@sourceware.org> (raw) https://gcc.gnu.org/g:04cdb132020733bedc36d14d61cce4246b8bbe4c commit r11-6795-g04cdb132020733bedc36d14d61cce4246b8bbe4c Author: Will Schmidt <will_schmidt@vnet.ibm.com> Date: Wed Jan 13 13:48:30 2021 -0600 [PATCH, rs6000] Update pr88233.c test (pr91799) Hi, This is a follow-up fix to clean up pr91799. Per review of test results, it appears that the combination of target and dg-require stanzas is not sufficient to properly limit the test to 64-bit only on darwin. This adds an additional dg-require clause to limit the test to 64-bit environments. Tested on power7 and power8 using assorted variations of make -k check-gcc-c "RUNTESTFLAGS=powerpc.exp=pr88233.c --target_board=unix/'{-mcpu=power7,-mcpu=power6,-mcpu=power8}''{-m32,-m64}'" PR target/91799 2021-01-19 Will Schmidt <will_schmidt@vnet.ibm.com> gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr88233.c: Update dg- stanzas. Diff: --- gcc/testsuite/gcc.target/powerpc/pr88233.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.target/powerpc/pr88233.c b/gcc/testsuite/gcc.target/powerpc/pr88233.c index 8e5f15b83b5..27c73717a3f 100644 --- a/gcc/testsuite/gcc.target/powerpc/pr88233.c +++ b/gcc/testsuite/gcc.target/powerpc/pr88233.c @@ -1,4 +1,4 @@ -/* { dg-do compile { target lp64 } } */ +/* { dg-require-effective-target lp64 } */ /* { dg-options "-O2 -mdejagnu-cpu=power8" } */ typedef struct { double a[2]; } A;
reply other threads:[~2021-01-19 17:43 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=20210119174345.A4C00384A031@sourceware.org \ --to=willschm@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).