public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104492] [12 Regression] Bogus dangling pointer warning at -O3 Date: Fri, 11 Feb 2022 00:49:11 +0000 [thread overview] Message-ID: <bug-104492-4-wvVHZ0HEjA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104492-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104492 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|c++ |middle-end Summary|Bogus dangling pointer |[12 Regression] Bogus |warning (dangling pointer |dangling pointer warning at |to ‘candidates’ may be used |-O3 |[-Werror=dangling-pointer=] | |) | Ever confirmed|0 |1 Blocks| |104077 Last reconfirmed| |2022-02-11 Keywords| |diagnostic CC| |msebor at gcc dot gnu.org --- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> --- The warning is issued for the if condition in the basic block below: <bb 28> [local count: 1014686340]: # _106 = PHI <&MEM <const struct QLatin1String[1]> [(void *)&candidates + 16B](26), &candidates(27)> <L14>: _274 = _106; __pred ={v} {CLOBBER(eol)}; _17 = _274; __pred ={v} {CLOBBER(eol)}; candidates ={v} {CLOBBER(eol)}; <<< clobber s ={v} {CLOBBER(eol)}; D.169975 ={v} {CLOBBER(eol)}; if (&MEM <const struct QLatin1String[1]> [(void *)&candidates + 16B] != _17) <<< -Wdangling-pointer goto <bb 30>; [5.50%] else goto <bb 29>; [94.50%] Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104077 [Bug 104077] bogus/missing -Wdangling-pointer
next prev parent reply other threads:[~2022-02-11 0:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-10 19:35 [Bug c++/104492] New: Bogus dangling pointer warning (dangling pointer to ‘candidates’ may be used [-Werror=dangling-pointer=]) thiago at kde dot org 2022-02-10 20:08 ` [Bug c++/104492] " pinskia at gcc dot gnu.org 2022-02-11 0:49 ` msebor at gcc dot gnu.org [this message] 2022-02-11 0:59 ` [Bug middle-end/104492] [12 Regression] Bogus dangling pointer warning at -O3 msebor at gcc dot gnu.org 2022-02-11 9:06 ` rguenth at gcc dot gnu.org 2022-02-15 0:40 ` msebor at gcc dot gnu.org 2022-03-09 13:07 ` rguenth at gcc dot gnu.org 2022-03-09 13:07 ` rguenth at gcc dot gnu.org 2022-03-16 16:01 ` msebor at gcc dot gnu.org 2022-04-20 8:52 ` jakub at gcc dot gnu.org 2022-04-25 8:43 ` rguenth at gcc dot gnu.org 2022-04-27 10:03 ` cvs-commit at gcc dot gnu.org 2022-04-27 10:03 ` rguenth at gcc dot gnu.org 2022-04-27 16:48 ` cvs-commit 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-104492-4-wvVHZ0HEjA@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).