public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/54202] Overeager warning about freeing non-heap objects
Date: Wed, 08 Aug 2012 14:00:00 -0000	[thread overview]
Message-ID: <bug-54202-4-Yz0S46U6xj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54202-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-08-08
     Ever Confirmed|0                           |1

--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-08-08 13:59:58 UTC ---
Confirmed.  This way it becomes an always may-be warning because a function
may not actually be executed (apart from main()).  Almost all warnings behave
this way btw.  GCC is in this case seeing

 free (&shared_null);

and considers this a good thing to warn on.

So would you consider printing

warning: possible attempt to free a non-heap object 'shared_null'

a fix?  Unconditionally, as we really cannot prove a line of code _will_
be executed at runtime (we can replace the free by an abort call though ...).


  reply	other threads:[~2012-08-08 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 13:36 [Bug c/54202] New: " thiago at kde dot org
2012-08-08 14:00 ` rguenth at gcc dot gnu.org [this message]
2012-08-08 14:22 ` [Bug c/54202] " thiago at kde dot org
2012-08-08 14:36 ` rguenth at gcc dot gnu.org
2012-08-08 14:53 ` thiago at kde dot org
2012-08-08 19:01 ` pinskia at gcc dot gnu.org
2020-11-03 19:50 ` [Bug middle-end/54202] " msebor at gcc dot gnu.org
2021-05-17 12:09 ` dangelog at gmail dot com
2021-06-16 13:19 ` mserdarsanli at gmail dot com
2021-06-16 16:35 ` msebor at gcc dot gnu.org
2023-08-25 11:46 ` charlechaud at gmail dot com

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-54202-4-Yz0S46U6xj@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).