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)] Compile prefix-ds-dq.c with -mno-strict-align Date: Sat, 30 Sep 2023 04:15:07 +0000 (GMT) [thread overview] Message-ID: <20230930041507.54AA93857027@sourceware.org> (raw) https://gcc.gnu.org/g:f8196b6e6539c627cfb2b3829b5e670df561165a commit f8196b6e6539c627cfb2b3829b5e670df561165a Author: Alexandre Oliva <oliva@adacore.com> Date: Fri Apr 14 23:53:24 2023 -0300 Compile prefix-ds-dq.c with -mno-strict-align In order for the expected asm to be generated, I found the need for -mno-strict-align, on toolchains that enable -mstrict-align by default. for gcc/testsuite/ChangeLog * gcc.target/powerpc/prefix-ds-dq.c: Disable -mstrict-align. Diff: --- gcc/testsuite/gcc.target/powerpc/prefix-ds-dq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.target/powerpc/prefix-ds-dq.c b/gcc/testsuite/gcc.target/powerpc/prefix-ds-dq.c index 554cd0c1bea..b2940fae6f4 100644 --- a/gcc/testsuite/gcc.target/powerpc/prefix-ds-dq.c +++ b/gcc/testsuite/gcc.target/powerpc/prefix-ds-dq.c @@ -1,7 +1,7 @@ /* { dg-do compile } */ /* { dg-require-effective-target powerpc_prefixed_addr } */ /* { dg-require-effective-target lp64 } */ -/* { dg-options "-O2 -mdejagnu-cpu=power10" } */ +/* { dg-options "-O2 -mdejagnu-cpu=power10 -mno-strict-align" } */ /* Tests whether we generate a prefixed load/store operation for addresses that don't meet DS/DQ offset constraints. 64-bit is needed for testing the use
next reply other threads:[~2023-09-30 4:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-30 4:15 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-10-19 6:01 Alexandre Oliva 2023-09-29 22:11 Alexandre Oliva 2023-04-06 6:34 Alexandre Oliva 2023-03-30 14:07 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 2022-04-27 21:29 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=20230930041507.54AA93857027@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: 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).