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/96564] [11/12/13 Regression] New maybe use of uninitialized variable warning since r11-959
Date: Tue, 14 Mar 2023 05:00:51 +0000	[thread overview]
Message-ID: <bug-96564-4-ltBjWZrxom@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96564-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note I don't think you really need exact aliasing information to optimize this
though. See PR 109119 for an example where you just need to know on the path
where PRE adds the load, the two addresses are equal due to the condition.

  parent reply	other threads:[~2023-03-14  5:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  7:30 [Bug middle-end/96564] New: New maybe use of uninitialized variable warning since GCC >10 stefansf at linux dot ibm.com
2020-08-11  9:27 ` [Bug middle-end/96564] " glisse at gcc dot gnu.org
2020-08-11  9:47 ` [Bug middle-end/96564] [11 Regression] New maybe use of uninitialized variable warning since r11-959 jakub at gcc dot gnu.org
2020-08-11 17:10 ` msebor at gcc dot gnu.org
2020-08-11 17:24 ` msebor at gcc dot gnu.org
2020-08-25  8:20 ` rguenth at gcc dot gnu.org
2021-01-14  9:19 ` rguenth at gcc dot gnu.org
2021-02-11 10:48 ` jakub at gcc dot gnu.org
2021-04-27 11:39 ` [Bug middle-end/96564] [11/12 " jakub at gcc dot gnu.org
2021-07-28  7:05 ` rguenth at gcc dot gnu.org
2022-04-21  7:48 ` rguenth at gcc dot gnu.org
2023-03-14  5:00 ` pinskia at gcc dot gnu.org [this message]
2023-05-29 10:03 ` [Bug middle-end/96564] [11/12/13/14 " jakub at gcc dot gnu.org
2024-03-10 22:49 ` law at gcc dot gnu.org
2024-03-11 10:23 ` rguenth at gcc dot gnu.org
2024-03-11 13:26 ` rguenth at gcc dot gnu.org
2024-03-11 15:20 ` amacleod at redhat dot com
2024-03-12  7:37 ` rguenth at gcc dot gnu.org
2024-05-16 11:23 ` [Bug middle-end/96564] [11/12/13/14/15 " rguenth at gcc dot gnu.org
2024-05-16 12:44 ` cvs-commit at gcc dot gnu.org
2024-05-16 14:27 ` aldyh 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-96564-4-ltBjWZrxom@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).