[vta] revamp bootstrap-debug with -fcompare-debug, fix LIBCFLAGS uses

[Alexandre Oliva]

On Oct  7, 2008, Adam Nemet <anemet@caviumnetworks.com> wrote:

> I think you also need to update install.texi.

Thanks for reminding me, I was indeed missing docs for the newly-added
BUILD_CONFIG as well.  Fixed as follows in the branch.  I also added
it the patch for the trunk I just posted in this thread, although
somewhat shortened, omitting features that are only in the VTA branch.
I also added a reference to bug 37137 to the top-level ChangeLog
entry, and dropped the cut&pasto that referenced bootstrap4-debug in
there.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: bootstrap-configs-doc.patch
Type: text/x-patch
Size: 3053 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20081010/f0289073/attachment.bin>
-------------- next part --------------

for  gcc/ChangeLog
from  Alexandre Oliva  <aoliva@redhat.com>

	PR target/37137
	* doc/install.texi (STAGE1_TFLAGS, BUILD_CONFIG): Document.

Index: gcc/doc/install.texi
===================================================================
--- gcc/doc/install.texi.orig	2008-10-01 15:43:57.000000000 -0300
+++ gcc/doc/install.texi	2008-10-10 05:08:11.000000000 -0300
@@ -1848,7 +1848,7 @@ bootstrapped, you can use @code{CFLAGS_F
 compilation flags, as for non-bootstrapped target libraries.
 Again, if the native compiler miscompiles the stage1 compiler, you may
 need to work around this by avoiding non-working parts of the stage1
-compiler.  Use @code{STAGE1_LIBCFLAGS} to this end.
+compiler.  Use @code{STAGE1_TFLAGS} to this end.
 
 If you used the flag @option{--enable-languages=@dots{}} to restrict
 the compilers to be built, only those you've actually enabled will be
@@ -1872,6 +1872,24 @@ the one you are building on: for example
 @code{powerpc64-unknown-linux-gnu} host.  In this case, pass
 @option{--enable-bootstrap} to the configure script.
 
+@code{BUILD_CONFIG} can be used to bring in additional customization to
+the build.  It can be set to a whitespace-separated list of names.  For
+each such @code{NAME}, top-level @file{config/@code{NAME}.mk} will be
+included by the top-level @file{Makefile}, bringing in any settings it
+contains.  Some examples are:
+
+@table @asis
+@item @samp{bootstrap-O1}
+Removes any @option{-O}-started option from @code{BOOT_CFLAGS}, and adds
+@option{-O1} to it.  @samp{BUILD_CONFIG=bootstrap-O1} is equivalent to
+@samp{BOOT_CFLAGS='-g -O1'}.
+
+@item @samp{bootstrap-O3}
+Analogous to @code{bootstrap-O1}.
+
+@item @samp{bootstrap-debug}
+Builds stage2 without debug information, and uses
+@file{contrib/compare-debug} to compare object files.
 
 @section Building a cross compiler
 


-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
FSFLA Board Member       ?S? Libre! => http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}