This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [3.3 branch] IA64 bootstrap failure
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: "'gcc at gcc dot gnu dot org '" <gcc at gcc dot gnu dot org>
- Date: Wed, 9 Jul 2003 00:32:24 -0400 (EDT)
- Subject: Re: [3.3 branch] IA64 bootstrap failure
On Tue, 8 Jul 2003, H. J. Lu wrote:
> On Tue, Jul 08, 2003 at 04:30:11PM -0700, Jim Wilson wrote:
> > On Tue, 2003-07-08 at 15:56, S. Bosscher wrote:
> > > Doesn't valgrind check for uninitialized/out-of-bounds memory refs?
> > Ah, yes, I keep forgetting about valgrind. Maybe I should try using it
> > someday.
> I tried valgrind with a cross compiler to ia64 from ix86. I didn't
> find anything serious:
>
> http://gcc.gnu.org/ml/gcc/2003-07/msg00084.html
It looks by "tried valgrind" you man running just plain valgrind
instead of configure --enable-checking=valgrind. The latter
would instrument the memory management inside GCC (and properly
handle the mmap end+1 thingy), so without it you would miss that
reused-pool-entries are actually uninitialized memory accesses.
brgds, H-P