public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] add explicit ABI and align options to pr88233.c
Date: Mon, 22 Apr 2024 05:13:45 +0000 (GMT)	[thread overview]
Message-ID: <20240422051345.1A6A13858C66@sourceware.org> (raw)

https://gcc.gnu.org/g:387ce53fd3fdaeefc7dc9d603df0d66495580fbf

commit 387ce53fd3fdaeefc7dc9d603df0d66495580fbf
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Apr 21 17:24:30 2024 -0300

    add explicit ABI and align options to pr88233.c
    
    We've observed failures of this test on powerpc configurations that
    default to different calling conventions and alignment requirements.
    Both settings are needed for the original expectations to be met.
    
    The test was later modified to have different expectations for big and
    little endian code generation.  This patch restores the original
    codegen expectations, that, with the explicit options, don't vary any
    more.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.target/powerpc/pr88233.c: Make some alignment strictness
            and calling conventions assumptions explicit.  Restore uniform
            codegen expectations

Diff:
---
 gcc/testsuite/gcc.target/powerpc/pr88233.c | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/gcc/testsuite/gcc.target/powerpc/pr88233.c b/gcc/testsuite/gcc.target/powerpc/pr88233.c
index 27c73717a3f..46a3ebfa287 100644
--- a/gcc/testsuite/gcc.target/powerpc/pr88233.c
+++ b/gcc/testsuite/gcc.target/powerpc/pr88233.c
@@ -1,5 +1,5 @@
 /* { dg-require-effective-target lp64 } */
-/* { dg-options "-O2 -mdejagnu-cpu=power8" } */
+/* { dg-options "-O2 -mdejagnu-cpu=power8 -mno-strict-align -fpcc-struct-return" } */
 
 typedef struct { double a[2]; } A;
 A
@@ -9,6 +9,5 @@ foo (const A *a)
 }
 
 /* { dg-final { scan-assembler-not {\mmtvsr} } } */
-/* { dg-final { scan-assembler-times {\mlxvd2x\M} 1 { target { be } } } } */
-/* { dg-final { scan-assembler-times {\mstxvd2x\M} 1 { target { be } } } } */
-/* { dg-final { scan-assembler-times {\mlfd\M} 2 { target { le } } } } */
+/* { dg-final { scan-assembler-times {\mlxvd2x\M} 1 } } */
+/* { dg-final { scan-assembler-times {\mstxvd2x\M} 1 } } */

             reply	other threads:[~2024-04-22  5:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22  5:13 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-28  5:21 Alexandre Oliva
2024-04-23  3:48 Alexandre Oliva
2024-04-23  2:39 Alexandre Oliva
2024-04-22  6:57 Alexandre Oliva
2024-04-22  2:41 Alexandre Oliva
2024-04-21 20:28 Alexandre Oliva
2023-04-06  6:34 Alexandre Oliva
2023-03-30 14:06 Alexandre Oliva
2023-03-24  6:24 Alexandre Oliva
2023-03-23  3:47 Alexandre Oliva
2023-03-16 14:22 Alexandre Oliva
2023-03-15 14:05 Alexandre Oliva
2021-03-11 10:21 Alexandre Oliva
2021-03-09 21:47 Alexandre Oliva
2021-03-09 21:25 Alexandre Oliva
2021-03-09  2:26 Alexandre Oliva

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=20240422051345.1A6A13858C66@sourceware.org \
    --to=aoliva@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: link
Be 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).