public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14885] Improper delete/free of local variables undetected
Date: Fri, 09 Apr 2004 19:03:00 -0000	[thread overview]
Message-ID: <20040409190301.28416.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040408003907.14885.ndeb@ece.cmu.edu>


------- Additional Comments From bangerth at dealii dot org  2004-04-09 19:03 -------
"PR" means "problem report", i.e. "bug report".

I don't mean to sweep it under the rug. My intention was this: we have
serious bugs where we fail to accept valid C++ code, or generate wrong code.
These bugs are way more important. If we have fixed all these, we can still
come around and invent techniques to diagnose user errors that probably
require solving the halting problem to catch all cases.

If this is of critical importance, feel free to pay one of the gcc developers
to implement this. I personally do not assign it significant importance, so
I go with Gaby's opinion to close the PR.

W.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14885


  parent reply	other threads:[~2004-04-09 19:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08  0:39 [Bug c++/14885] New: " ndeb at ece dot cmu dot edu
2004-04-08  0:41 ` [Bug c++/14885] " ndeb at ece dot cmu dot edu
2004-04-08  0:48 ` pinskia at gcc dot gnu dot org
2004-04-08 18:43 ` bangerth at dealii dot org
2004-04-08 19:55 ` gdr at integrable-solutions dot net
2004-04-08 20:11 ` ndeb at ece dot cmu dot edu
2004-04-09 19:03 ` bangerth at dealii dot org [this message]
2004-04-10  2:36 ` ndeb at ece dot cmu dot edu
2004-04-11 12:39 ` bangerth at dealii dot 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=20040409190301.28416.qmail@sources.redhat.com \
    --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).