Re: bootstrap failure on darwin, compare stages

[Andreas Tobler <toa at pop dot agri dot ch>]

Dale Johannesen wrote:

> I usually approach it this way:
> Get a "good" compiler (built with cc, usually) and the "bad" (stage2)
> compiler.
> Compile the file that differs with both compilers using -da.

-da ?

> Compare the dump files to get some idea what phase the problem is in.

 -v 'make -s file with asm output' (don't know the switch right now.)?

> Step through the compilers in parallel with the debugger, to find the place
>    where the bad code is.

I don't like to say this, but with gdb I have my probs, I remember vc++, sorry.
I find it easier to dbg a file which fails than a comparison stage. Here
I'm unsure who/what is responsible for.

> I haven't bootstrapped recently, I'll try it now.

Good luck
Andreas

and thx!!