public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106393] Add warnings for common dangling problems
Date: Thu, 13 Jun 2024 13:53:52 +0000	[thread overview]
Message-ID: <bug-106393-4-fjcjm2jTGk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106393-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106393

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #3)
> (In reply to Marek Polacek from comment #2)
> > The rest may have to be implemented in the analyzer.
> 
> Hm, let's ask David?

Please open it as a fresh bug against "analyzer", cite the specific test cases
you'd like it to handle, reference this bug, and add the new bug to the C++
analyzer tracker (bug 97110).

Note that to avoid burnout I'm still focusing on C for GCC 15.

      parent reply	other threads:[~2024-06-13 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 18:31 [Bug c++/106393] New: " redi at gcc dot gnu.org
2022-07-21 20:21 ` [Bug c++/106393] " mpolacek at gcc dot gnu.org
2022-10-26 19:14 ` cvs-commit at gcc dot gnu.org
2022-10-26 19:15 ` mpolacek at gcc dot gnu.org
2024-06-12 21:30 ` egallager at gcc dot gnu.org
2024-06-13 13:53 ` dmalcolm 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-106393-4-fjcjm2jTGk@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).