public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/101020] [12 regression] Several test case failures after r12-1316 Date: Fri, 11 Jun 2021 02:43:08 +0000 [thread overview] Message-ID: <bug-101020-4-TaSHuoxfxa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101020-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101020 luoxhu at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org, | |segher at kernel dot crashing.org --- Comment #1 from luoxhu at gcc dot gnu.org --- Confirmed. The BE-m32 test is a nightmare to me... :( For float128-call.c, need check target BE or LE. And for pr100085.c, vector __int128 is not supported with {-m32}, just skip it. Ok to trunk? [PATCH] rs6000: Fix test case failures by PR100085 [PR101020] gcc/testsuite/ChangeLog: PR target/101020 * gcc.target/powerpc/float128-call.c: Adjust. * gcc.target/powerpc/pr100085.c: Likewise. --- gcc/testsuite/gcc.target/powerpc/float128-call.c | 6 ++++-- gcc/testsuite/gcc.target/powerpc/pr100085.c | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/gcc/testsuite/gcc.target/powerpc/float128-call.c b/gcc/testsuite/gcc.target/powerpc/float128-call.c index a1f09df..b64ffc6 100644 --- a/gcc/testsuite/gcc.target/powerpc/float128-call.c +++ b/gcc/testsuite/gcc.target/powerpc/float128-call.c @@ -21,5 +21,7 @@ TYPE one (void) { return ONE; } void store (TYPE a, TYPE *p) { *p = a; } -/* { dg-final { scan-assembler "lvx 2" } } */ -/* { dg-final { scan-assembler "stvx 2" } } */ +/* { dg-final { scan-assembler {\mlxvd2x 34\M} {target be} } } */ +/* { dg-final { scan-assembler {\mstxvd2x 34\M} {target be} } } */ +/* { dg-final { scan-assembler {\mlvx 2\M} {target le} } } */ +/* { dg-final { scan-assembler {\mstvx 2\M} {target le} } } */ diff --git a/gcc/testsuite/gcc.target/powerpc/pr100085.c b/gcc/testsuite/gcc.target/powerpc/pr100085.c index 7d8b147..b6738ea 100644 --- a/gcc/testsuite/gcc.target/powerpc/pr100085.c +++ b/gcc/testsuite/gcc.target/powerpc/pr100085.c @@ -1,4 +1,4 @@ -/* { dg-do compile } */ +/* { dg-do compile {target lp64} } */ /* { dg-options "-O2 -mdejagnu-cpu=power8" } */
next prev parent reply other threads:[~2021-06-11 2:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-10 17:03 [Bug testsuite/101020] New: " seurer at gcc dot gnu.org 2021-06-11 2:43 ` luoxhu at gcc dot gnu.org [this message] 2021-06-11 8:02 ` [Bug testsuite/101020] " rguenth at gcc dot gnu.org 2021-06-11 13:16 ` dje at gcc dot gnu.org 2021-06-15 1:07 ` cvs-commit at gcc dot gnu.org 2021-06-16 0:57 ` luoxhu 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-101020-4-TaSHuoxfxa@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).