From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: is+guile@kaidea.freeserve.co.uk, bug-guile@gnu.org
Subject: Re: [PATCH] reducing uninitialized memory warnings
Date: 04 Oct 2002 00:23:40 +0200 [thread overview]
Message-ID: <87vg4jupoz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m37kgzgqka.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> Marius> Since this reduction is so small, I'm inclined not to
> Marius> apply your patch. What do others say?
>
> Do the warnings indicate real problems, or are they false positives?
> If real, we should fix them; if false, we shouldn't, because the fix
> will generally impact performance, and instead we should send a report
> to valgrind.
The way I understand it, they are false positives. The warnings come
when Guile is conservatively marking pointers in a region that hasn't
been fully initialized.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2002-10-03 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 18:10 [PATCH] reducing uninitialized memory warnings I.Sheldon
2002-10-03 18:03 ` Marius Vollmer
2002-10-03 21:28 ` Neil Jerram
2002-10-03 22:23 ` Marius Vollmer [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=87vg4jupoz.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@gnu.org \
--cc=is+guile@kaidea.freeserve.co.uk \
/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).