public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/115199] [15 regression] gettext (libtextstyle) testsuite miscompiled
Date: Wed, 22 May 2024 21:43:55 +0000	[thread overview]
Message-ID: <bug-115199-4-EwFGRSa3D9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115199-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |15.0
             Status|UNCONFIRMED                 |NEW
                 CC|                            |rguenth at gcc dot gnu.org
           Keywords|                            |alias
   Last reconfirmed|                            |2024-05-22
     Ever confirmed|0                           |1

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
```
  Deleted dead call: # .MEM_6 = VDEF <.MEM_4>
# PT = null { D.2790 }
# ALIGN = 8, MISALIGN = 0
e_7 = memcpyD.1670 (f_5, "z", 1);
```

Note the volatile makes the difference. It seems like we miss that the memory
escapes through the volatile store so we delete the memcpy as being dead.

  parent reply	other threads:[~2024-05-22 21:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 21:28 [Bug tree-optimization/115199] New: " sjames at gcc dot gnu.org
2024-05-22 21:28 ` [Bug tree-optimization/115199] " sjames at gcc dot gnu.org
2024-05-22 21:35 ` sjames at gcc dot gnu.org
2024-05-22 21:42 ` kacper.slominski72 at gmail dot com
2024-05-22 21:43 ` pinskia at gcc dot gnu.org [this message]
2024-05-22 21:46 ` [Bug tree-optimization/115199] [15 regression] gettext (libtextstyle) testsuite miscompiled since r15-579 jakub at gcc dot gnu.org
2024-05-23  8:59 ` rguenth at gcc dot gnu.org
2024-05-23 12:39 ` cvs-commit at gcc dot gnu.org
2024-05-23 12:40 ` rguenth 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-115199-4-EwFGRSa3D9@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).