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/105867] [12/13 Regression] incorrect dangling-pointer warning
Date: Tue, 07 Jun 2022 06:05:50 +0000 [thread overview]
Message-ID: <bug-105867-4-DWXA0RwyP0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105867-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105867
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-06-07
Summary|incorrect dangling-pointer |[12/13 Regression]
|warning |incorrect dangling-pointer
| |warning
Status|UNCONFIRMED |NEW
Component|middle-end |tree-optimization
Target Milestone|--- |12.2
Ever confirmed|0 |1
Keywords| |diagnostic
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Looks the warning does not notice the store was "undone" with later on.
We have:
MEM[(struct ConsList *)this_3(D) + 8B].value = currNode_5(D);
MEM[(struct ConsList *)this_3(D) + 8B].tail = &guard.oldNodeStack;
....
<bb 5> [local count: 118111600]:
MEM[(struct ConsList *)this_3(D) + 8B] = guard.oldNodeStack;
guard ={v} {CLOBBER};
guard ={v} {CLOBBER(eol)};
return;
The store to this removes the stored address of the local variable.
Confirmed.
next prev parent reply other threads:[~2022-06-07 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 0:13 [Bug middle-end/105867] New: " gman at chromium dot org
2022-06-07 6:05 ` pinskia at gcc dot gnu.org [this message]
2022-07-25 16:10 ` [Bug tree-optimization/105867] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-11-13 9:32 ` agriff at tin dot it
2023-03-20 10:48 ` wielkiegie at gmail dot com
2023-05-08 12:24 ` [Bug tree-optimization/105867] [12/13/14 " 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-105867-4-DWXA0RwyP0@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).