From: Zack Weinberg <zack@codesourcery.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: RFC: --enable-checking=valgrind.
Date: Sun, 10 Nov 2002 19:34:00 -0000 [thread overview]
Message-ID: <20021111033455.GC11507@egil.codesourcery.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0211102024070.57197-100000@dair.pair.com>
On Sun, Nov 10, 2002 at 08:35:36PM -0500, Hans-Peter Nilsson wrote:
> A conceptual patch. Bootstrap still in progress on
> i686-pc-linux-gnu. Lots of bug indications so far...
I bet many of those indications will go away if you add annotations to
cppfiles.c so that it knows what's going on with mmap(). valgrind
defines the accessible memory area of an mmap region to be precisely
the size passed to mmap; cpplib will touch one byte beyond that (it
knows that the kernel will round up the region to a page boundary and
zero-fill the intervening space).
zw
next prev parent reply other threads:[~2002-11-11 3:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 17:35 Hans-Peter Nilsson
2002-11-10 19:34 ` Zack Weinberg [this message]
2002-11-11 1:55 ` Hans-Peter Nilsson
2002-11-11 16:53 ` Zack Weinberg
2002-11-11 17:48 ` Hans-Peter Nilsson
2002-11-12 6:02 ` Jan Hubicka
2002-11-12 17:11 ` Hans-Peter Nilsson
2002-11-12 17:21 ` Zack Weinberg
2002-11-13 5:32 ` Jan Hubicka
2002-11-13 13:38 ` Hans-Peter Nilsson
2002-11-18 17:20 ` Richard Henderson
2002-11-18 18:24 ` [RFA:] Take 2 (was: Re: RFC: --enable-checking=valgrind.) Hans-Peter Nilsson
2002-11-18 20:37 ` Richard Henderson
2002-11-20 11:57 ` Hans-Peter Nilsson
2002-11-18 22:12 ` Neil Booth
2002-11-19 4:37 ` Hans-Peter Nilsson
2002-11-18 22:33 ` Andreas Jaeger
2002-11-19 4:33 ` Hans-Peter Nilsson
2002-11-19 7:31 ` Andreas Jaeger
2002-11-19 9:07 ` Hans-Peter Nilsson
2002-11-19 9:15 ` [RFA:] Take 2 Andreas Jaeger
2002-11-26 5:42 ` [PATCH] Fix configure (was Re: [RFA:] Take 2 (was: Re: RFC: --enable-checking=valgrind.)) Jakub Jelinek
2002-11-26 9:59 ` Richard Henderson
2002-11-28 7:34 ` Hans-Peter Nilsson
2002-11-28 8:08 ` Hans-Peter Nilsson
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=20021111033455.GC11507@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@bitrange.com \
/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).