public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/97301] [11 regression] gcc.target/powerpc/sse-movlps-1.c fails after r11-3434
Date: Fri, 22 Jan 2021 12:08:06 +0000	[thread overview]
Message-ID: <bug-97301-4-Jiw49zpTz8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97301-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97301

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think the right fix is:
2021-01-22  Jakub Jelinek  <jakub@redhat.com>

        PR testsuite/97301
        * config/rs6000/mmintrin.h (__m64): Add __may_alias__ attribute.

--- gcc/config/rs6000/mmintrin.h.jj     2021-01-04 10:25:46.794143679 +0100
+++ gcc/config/rs6000/mmintrin.h        2021-01-22 13:03:28.511043929 +0100
@@ -58,7 +58,8 @@
 #include <altivec.h>
 /* The Intel API is flexible enough that we must allow aliasing with other
    vector types, and their scalar components.  */
-typedef __attribute__ ((__aligned__ (8))) unsigned long long __m64;
+typedef __attribute__ ((__aligned__ (8),
+                       __may_alias__)) unsigned long long __m64;

 typedef __attribute__ ((__aligned__ (8)))
 union
which will then match the ppc64le *intrin.h emulation match what x86 is doing
TBAA-wise.  x86 mmintrin.h has:
typedef int __m64 __attribute__ ((__vector_size__ (8), __may_alias__));

  parent reply	other threads:[~2021-01-22 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06  1:03 [Bug other/97301] New: " seurer at gcc dot gnu.org
2020-10-06  9:09 ` [Bug ipa/97301] " rguenth at gcc dot gnu.org
2020-10-16 12:11 ` [Bug testsuite/97301] " rguenth at gcc dot gnu.org
2021-01-14  9:24 ` rguenth at gcc dot gnu.org
2021-01-22 12:08 ` jakub at gcc dot gnu.org [this message]
2021-01-23  8:43 ` cvs-commit at gcc dot gnu.org
2021-01-23  8:43 ` jakub at gcc dot gnu.org
2021-01-29 19:19 ` cvs-commit at gcc dot gnu.org
2021-04-20 23:31 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:50 ` cvs-commit 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-97301-4-Jiw49zpTz8@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: 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).