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)] use -mno-strict-align for strlenopt-80.c on powerpc Date: Tue, 9 Mar 2021 21:47:13 +0000 (GMT) [thread overview] Message-ID: <20210309214713.98B4A385F01F@sourceware.org> (raw) https://gcc.gnu.org/g:c38a149840c5e0572c8ae9cd82aa4781feab9100 commit c38a149840c5e0572c8ae9cd82aa4781feab9100 Author: Alexandre Oliva <oliva@adacore.com> Date: Tue Mar 9 18:42:54 2021 -0300 use -mno-strict-align for strlenopt-80.c on powerpc ppc configurations that have -mstrict-align enabled by default fail gcc.dg/strlenopt-80.c, because some memcpy calls don't get turned into MEM_REFs, which defeats the tested-for strlen optimization. for gcc/testsuite/ChangeLog * gcc.dg/strlenopt-80.c: Add -mno-strict-align on ppc. Diff: --- gcc/testsuite/gcc.dg/strlenopt-80.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/strlenopt-80.c b/gcc/testsuite/gcc.dg/strlenopt-80.c index 9124fe4740a..104a5e509fd 100644 --- a/gcc/testsuite/gcc.dg/strlenopt-80.c +++ b/gcc/testsuite/gcc.dg/strlenopt-80.c @@ -5,7 +5,11 @@ such a store. { dg-do compile { target aarch64*-*-* i?86-*-* powerpc*-*-* x86_64-*-* } } - { dg-options "-O2 -Wall -fdump-tree-optimized" } */ + { dg-options "-O2 -Wall -fdump-tree-optimized" } + + On powerpc configurations that have -mno-strict-alignment by default, + the memcpy calls for ncpylog >= 3 are not turned into MEM_REFs. + { dg-additional-options "-mno-strict-align" { target powerpc*-*-* } } */ #define CHAR_BIT __CHAR_BIT__ #define SIZE_MAX __SIZE_MAX__
next reply other threads:[~2021-03-09 21:47 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-09 21:47 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-10-19 6:00 Alexandre Oliva 2023-09-30 4:15 Alexandre Oliva 2023-09-29 22:11 Alexandre Oliva 2023-04-06 6:33 Alexandre Oliva 2023-03-30 14:06 Alexandre Oliva 2023-03-24 6:24 Alexandre Oliva 2023-03-23 3:46 Alexandre Oliva 2023-03-16 14:21 Alexandre Oliva 2023-03-15 14:04 Alexandre Oliva 2021-03-11 10:21 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=20210309214713.98B4A385F01F@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).