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: "S. Bosscher" <S dot Bosscher at student dot tudelft dot nl>
- To: 'Jim Wilson ' <wilson at tuliptree dot org>, 'Andreas Schwab ' <schwab at suse dot de>
- Cc: "'gcc at gcc dot gnu dot org '" <gcc at gcc dot gnu dot org>
- Date: Wed, 09 Jul 2003 00:56:45 +0200
- Subject: RE: [3.3 branch] IA64 bootstrap failure
Jim Wilson wrote:
>
> Andreas Schwab wrote:
> > Running the same (stage2) compiler command on the command line
> produces
> > output that is the same as the output from the stage1 compiler. So it
> > indeed looks like it's dependent on the environment size.
>
> I've debugged problems like this before. You vary the environment size
> until you can reproduce the problem, and then you debug two compilers in
> parallel with different environment sizes until you figure out why they
> emit different code. Probably an uninitialized variable or a
> stray/out-of-bounds memory reference somewhere. Another possibly is
> that addresses are being used (e.g. in a hash table) and there is a
> latent bug in the code.
Doesn't valgrind check for uninitialized/out-of-bounds memory refs?
Gr.
Steven