This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Example of debugging GCC with toplevel bootstrap
- From: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
- To: Diego Novillo <dnovillo at redhat dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 05 Jan 2006 09:40:10 +0100
- Subject: Re: Example of debugging GCC with toplevel bootstrap
- References: <43B8E567.8080300@lu.unisi.ch> <200601041712.04399.dnovillo@redhat.com>
make all-stage2 STAGE1_LANGUAGES=c,fortran
So, how would I now get a cc1plus/f951/jc1/cc1 binary compiled by the
stage0 (host) compiler?
That would give me the 4 '-g -O0' binaries compiled with the system
compiler. I've tried following these notes, but it always gives me
binaries built by 'prev-gcc/xgcc'.
My notes were for a miscompilation, so I also needed the stage2
binaries, built by prev-gcc/xgcc.
make stage1-bubble STAGE1_LANGUAGES=c,c++,fortran,java
I think that after I fix PR25670, as a side effect, you will also be
able to use the more intuitive target "all-stage1". But I didn't think
of that PR much closely because it is about a target that was anyway
undocumented, and there are bigger fish to fry.
Paolo