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 middle-end/115539] Misoptimization of application at -O2 -g on x86-64 causing segfaults on valid memory accesses where it works on both clang and gcc at -g (no -O2)
Date: Tue, 18 Jun 2024 16:09:35 +0000	[thread overview]
Message-ID: <bug-115539-4-0BCAHCaesX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115539-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c                           |middle-end
           Keywords|                            |alias

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The places which are just as likely cause strict aliasing issues:
geteaw
geteal
geteaw_mem
geteal_mem

      parent reply	other threads:[~2024-06-18 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 11:55 [Bug c/115539] New: " melodygoad18 at gmail dot com
2024-06-18 11:59 ` [Bug c/115539] " schwab@linux-m68k.org
2024-06-18 12:08 ` melodygoad18 at gmail dot com
2024-06-18 12:09 ` melodygoad18 at gmail dot com
2024-06-18 12:27 ` jakub at gcc dot gnu.org
2024-06-18 12:46 ` sjames at gcc dot gnu.org
2024-06-18 12:47 ` sjames at gcc dot gnu.org
2024-06-18 12:47 ` sjames at gcc dot gnu.org
2024-06-18 16:09 ` pinskia 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-115539-4-0BCAHCaesX@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).