------- Comment #3 from pinskia at gcc dot gnu dot org 2007-05-18 04:10 ------- I have no idea what you are talking about overwritting. In 4.1 and before the subdirectory gcc's makefile handled bootstrap (staging). In 4.2 and above, the toplevel makefile handles bootstrap. So that means we can configure the gcc subdirectory differently for the two different stages which is exactly what happens with --enable-stage1-checking=*. When stage1 is configured, the toplevel makefile passes down the --enable-checking=x for what --enable-stage1-checking= says to do (defaults to yes). So you will not see a -DENABLE_CHECKING on the command line when compiling stage1 at all. You will see in stage1-gcc (when the build finishes if you don't use make bootstrap-lean) in auto-host.h, a define for ENABLE_CHECKING. This option is really only useful for disable checking for stage1 when you are short on resources (memory/time).
Plus configure is setup correctly to enable more checking for stage1. Also this is the help from configure: choose additional checking for stage1 of the compiler. Which is exactly what it does. It means enable checking in the product of stage1 (the stage1 compiler) which is a good description I think. It means compiling stage2 is going to be slower if you enable all checking for stage1. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31963
