From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: build failures from gcc warning about memset
Date: Mon, 26 Oct 2009 10:26:49 +0100 [thread overview]
Message-ID: <87skd6h5eu.fsf@gnu.org> (raw)
In-Reply-To: m3d44bm8ov.fsf@pobox.com
Hello,
Andy Wingo <wingo@pobox.com> writes:
> Actually scm_gc_malloc will give you back a zeroed array, afaik, as
> GC_malloc does. The patch looks fine but if we can rely on
> scm_gc_malloc's new behavior, we don't need the memset at all.
Oh oh, good catch! It’s actually documented this way in
gcinterface.html and [0] but not in gc.h.
Anyway, I’ve fixed it now!
Thanks,
Ludo’.
[0] http://www.hpl.hp.com/personal/Hans_Boehm/gc/simple_example.html
prev parent reply other threads:[~2009-10-26 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 17:16 build failures from gcc warning about memset Julian Graham
2009-10-25 22:03 ` Ludovic Courtès
2009-10-25 22:04 ` Andy Wingo
2009-10-26 9:26 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skd6h5eu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).