From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] scripts: add sample model file for Coverity Scan
Date: Wed, 19 Mar 2014 17:47:11 +0100 [thread overview]
Message-ID: <5329CA0F.4040900@redhat.com> (raw)
In-Reply-To: <87siqerxkl.fsf@blackfin.pond.sub.org>
Il 19/03/2014 16:56, Markus Armbruster ha scritto:
>
>> > Given the results, okay to
>> > use the limited model where realloc never frees and malloc(0) returns
>> > non-NULL?
> I'd describe realloc() as "always frees the old block, returns a new
> block, which is never null". We might mean the same.
Yes, that's what I would do too, but it misses an important difference
between malloc() and realloc().
"If size is 0, then malloc() returns either NULL, or a unique pointer
value that can later be successfully passed to free()". Instead, for
realloc, "if size is equal to zero, and ptr is not NULL, then the call
is equivalent to free(ptr)" and presumably must return NULL.
So I'm doubly cheating by giving realloc(foo, 0) free+malloc semantics
instead of free.
BTW, this means that the handy "malloc(0) really means malloc(1)"
semantics are inconsistent because you cannot implement realloc(foo, 0)
that way.
Paolo
> Go ahead with the lying^Wlimited model, with a big, fat comment
> explaining our reasons.
next prev parent reply other threads:[~2014-03-19 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 17:03 [Qemu-devel] [PATCH] scripts: add sample model file for Coverity Scan Paolo Bonzini
2014-03-18 18:40 ` Markus Armbruster
2014-03-19 7:03 ` Paolo Bonzini
2014-03-19 9:08 ` Markus Armbruster
2014-03-19 12:46 ` Paolo Bonzini
2014-03-19 13:56 ` Paolo Bonzini
2014-03-19 14:57 ` Paolo Bonzini
2014-03-19 15:56 ` Markus Armbruster
2014-03-19 16:47 ` Paolo Bonzini [this message]
2014-03-19 9:36 ` Kevin Wolf
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=5329CA0F.4040900@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 NNTP newsgroup(s).