public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106868] [12 Regression] Bogus -Wdangling-pointer warning with -O1 Date: Mon, 12 Dec 2022 11:20:33 +0000 [thread overview] Message-ID: <bug-106868-4-3Mz59n1vsi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106868-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106868 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:ad6ace70ba38d2052eeb5adb9672d33f59867be0 commit r12-8972-gad6ace70ba38d2052eeb5adb9672d33f59867be0 Author: Richard Biener <rguenther@suse.de> Date: Mon Dec 5 10:13:13 2022 +0100 tree-optimization/106868 - bogus -Wdangling-pointer diagnostic The testcase shows we mishandle the case where there's a pass-through of a pointer through a function like memcpy. The following adjusts handling of this copy case to require a taken address and adjust the PHI case similarly. PR tree-optimization/106868 * gimple-ssa-warn-access.cc (pass_waccess::gimple_call_return_arg_ref): Inline into single user ... (pass_waccess::check_dangling_uses): ... here and adjust the call and the PHI case to require that ref.aref is the address of the decl. * gcc.dg/Wdangling-pointer-pr106868.c: New testcase. (cherry picked from commit d492d50f644811327c5976e2c918ab6d906ed40c)
next prev parent reply other threads:[~2022-12-12 11:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-07 8:47 [Bug c/106868] New: " medhefgo at web dot de 2022-09-07 9:05 ` [Bug tree-optimization/106868] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-09-12 16:18 ` msebor at gcc dot gnu.org 2022-09-12 17:04 ` msebor at gcc dot gnu.org 2022-12-05 9:41 ` rguenth at gcc dot gnu.org 2022-12-05 13:56 ` cvs-commit at gcc dot gnu.org 2022-12-05 14:06 ` rguenth at gcc dot gnu.org 2022-12-12 11:20 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-12 11:20 ` [Bug tree-optimization/106868] [12 " 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-106868-4-3Mz59n1vsi@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).