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: Thu, 30 Mar 2023 14:06:30 +0000 (GMT)	[thread overview]
Message-ID: <20230330140630.AAEC03858410@sourceware.org> (raw)

https://gcc.gnu.org/g:8920123c5228dfd876f6703c71f5168d3983f2e8

commit 8920123c5228dfd876f6703c71f5168d3983f2e8
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Mar 30 05:06:21 2023 -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 | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gcc/testsuite/gcc.dg/strlenopt-80.c b/gcc/testsuite/gcc.dg/strlenopt-80.c
index a8adbf1eed5..ec9a6ad85f7 100644
--- a/gcc/testsuite/gcc.dg/strlenopt-80.c
+++ b/gcc/testsuite/gcc.dg/strlenopt-80.c
@@ -8,6 +8,10 @@
    { dg-options "-O2 -Wall -fdump-tree-optimized" }
    { dg-additional-options "-msse" { target i?86-*-* x86_64-*-* } } */
 
+/* On powerpc configurations that have -mstrict-align 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__
 #define LEN_MAX       (__PTRDIFF_MAX__ - 2)

             reply	other threads:[~2023-03-30 14:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 14:06 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-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: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=20230330140630.AAEC03858410@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).