public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110091] [12/13/14 Regression] bogus -Wdangling-pointer on non-pointer values
Date: Fri, 12 Jan 2024 14:13:43 +0000 [thread overview]
Message-ID: <bug-110091-4-YnQhQaJvKm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110091-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110091
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |hubicka at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Honza? Why do we consider to split before anotherfunc(5)? It's an odd
place since we'll always arrive there from the point we insert the call?
The only other sensible point would have been before if (out), thus
BB4?
prev parent reply other threads:[~2024-01-12 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 12:00 [Bug middle-end/110091] New: " patrickdepinguin at gmail dot com
2023-06-02 22:05 ` [Bug tree-optimization/110091] " pinskia at gcc dot gnu.org
2023-06-02 22:07 ` [Bug tree-optimization/110091] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-01-10 15:40 ` jamborm at gcc dot gnu.org
2024-01-12 14:13 ` rguenth 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-110091-4-YnQhQaJvKm@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).