public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "agriff at tin dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105867] [12/13 Regression] incorrect dangling-pointer warning Date: Sun, 13 Nov 2022 09:32:54 +0000 [thread overview] Message-ID: <bug-105867-4-CuMROYduGp@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 Andrea Griffini <agriff at tin dot it> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |agriff at tin dot it --- Comment #4 from Andrea Griffini <agriff at tin dot it> --- Created attachment 53891 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53891&action=edit Simpler version that triggers the bug This code compiled on 12.2.0 with -O3 -Wall generates a warning about storing the address of a local variable. Surprisingly (for me) adding either of the two `printf` statements makes the warning go away. The code seems correct to me; a doubly linked list of all instances of Node is kept by inserting nodes in constructor and removing them in destructor.
next prev parent reply other threads:[~2022-11-13 9:32 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 ` [Bug tree-optimization/105867] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-07-25 16:10 ` rguenth at gcc dot gnu.org 2022-11-13 9:32 ` agriff at tin dot it [this message] 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-CuMROYduGp@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: linkBe 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).