public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/21320] possible false positives for '$foo may be used uninitialized in this function'
Date: Mon, 09 May 2005 21:23:00 -0000	[thread overview]
Message-ID: <20050509212333.17074.qmail@sourceware.org> (raw)
In-Reply-To: <20050501164321.21320.olh@suse.de>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-09 21:23 -------
Reduced testcase:
void *g();

static void *count_and_verify_instructions(int *ninst,const unsigned char *p)
{
   if (p == ((void *)0))
    return g();
 *ninst = 0;
 return 0;
}
void f(int);
void *decode_window(const unsigned char *data)
{
  int ninst;
  void *svn_err__temp = count_and_verify_instructions(&ninst, data);
  if (svn_err__temp)
    return svn_err__temp;

  f (ninst);
  return 0;
}


So this is not a bug at all because g (svn_error_createf) could return null.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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


  parent reply	other threads:[~2005-05-09 21:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01 16:43 [Bug c/21320] New: " olh at suse dot de
2005-05-01 16:44 ` [Bug c/21320] " olh at suse dot de
2005-05-01 16:45 ` [Bug middle-end/21320] " pinskia at gcc dot gnu dot org
2005-05-09 21:23 ` pinskia at gcc dot gnu dot org [this message]
2005-05-11  6:17 ` olh at suse dot de
2005-05-11 10:43 ` pinskia at gcc dot gnu dot org
2005-06-03 14:17 ` pinskia at gcc dot gnu 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=20050509212333.17074.qmail@sourceware.org \
    --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).