public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114676] [12/13/14 Regression] DSE removes assignment that is used later
Date: Tue, 23 Apr 2024 08:17:48 +0000	[thread overview]
Message-ID: <bug-114676-4-1HNlupNfSx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114676-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andreas Krebbel <krebbel@gcc.gnu.org>:

https://gcc.gnu.org/g:42189f21b22c43ac8ab46edf5f6a7b4d99bc86a5

commit r14-10087-g42189f21b22c43ac8ab46edf5f6a7b4d99bc86a5
Author: Andreas Krebbel <krebbel@linux.ibm.com>
Date:   Tue Apr 23 10:05:46 2024 +0200

    s390x: Fix vec_xl/vec_xst type aliasing [PR114676]

    The requirements of the vec_xl/vec_xst intrinsincs wrt aliasing of the
    pointer argument are not really documented.  As it turns out, users
    are likely to get it wrong.  With this patch we let the pointer
    argument alias everything in order to make it more robust for users.

    gcc/ChangeLog:

            PR target/114676
            * config/s390/s390-c.cc (s390_expand_overloaded_builtin): Use a
            MEM_REF with an addend of type ptr_type_node.

    gcc/testsuite/ChangeLog:

            PR target/114676
            * gcc.target/s390/zvector/pr114676.c: New test.

    Suggested-by: Jakub Jelinek <jakub@redhat.com>

      parent reply	other threads:[~2024-04-23  8:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 10:52 [Bug tree-optimization/114676] New: " aleksei.nikiforov at linux dot ibm.com
2024-04-10 11:06 ` [Bug target/114676] " pinskia at gcc dot gnu.org
2024-04-10 11:22 ` aleksei.nikiforov at linux dot ibm.com
2024-04-10 11:25 ` pinskia at gcc dot gnu.org
2024-04-10 11:28 ` aleksei.nikiforov at linux dot ibm.com
2024-04-10 11:33 ` pinskia at gcc dot gnu.org
2024-04-10 13:40 ` jakub at gcc dot gnu.org
2024-04-10 16:47 ` rguenth at gcc dot gnu.org
2024-04-11 12:30 ` krebbel at gcc dot gnu.org
2024-04-11 12:35 ` jakub at gcc dot gnu.org
2024-04-11 12:36 ` jakub at gcc dot gnu.org
2024-04-11 15:48 ` krebbel at gcc dot gnu.org
2024-04-12 13:32 ` law at gcc dot gnu.org
2024-04-12 18:36 ` sjames at gcc dot gnu.org
2024-04-17 17:01 ` krebbel at gcc dot gnu.org
2024-04-17 17:34 ` jakub at gcc dot gnu.org
2024-04-18 14:29 ` aleksei.nikiforov at linux dot ibm.com
2024-04-22  9:37 ` krebbel at gcc dot gnu.org
2024-04-23  8:17 ` cvs-commit at gcc dot gnu.org [this message]

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-114676-4-1HNlupNfSx@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).