------- Additional Comments From v dot haisman at sh dot cvut dot cz  
2005-01-04 21:24 -------
Subject: Re:  Bootstrap ignores compiler flags supplied
 on command line


I think that you have closed this one a bit too quick. Have you actually tried
it? This is what I have used:

CFLAGS="-O0 -g3 -fno-omit-frame-pointer" BOOT_CFLAGS="-O0 -g3
-fno-omit-frame-pointer" LIBCFLAGS="-O0 -g3 -fno-omit-frame-pointer"
LIBGCC2_CFLAGS="-O0 -g3 -fno-omit-frame-pointer" make CFLAGS="-O0 -g3
-fno-omit-frame-pointer" BOOT_CFLAGS="-O0 -g3 -fno-omit-frame-pointer"
LIBCFLAGS="-O0 -g3 -fno-omit-frame-pointer" LIBGCC2_CFLAGS="-O0 -g3
-fno-omit-frame-pointer" bootstrap

CFLAGS="-O0 -g3 -fno-omit-frame-pointer" BOOT_CFLAGS="-O0 -g3
-fno-omit-frame-pointer" LIBCFLAGS="-O0 -g3 -fno-omit-frame-pointer"
LIBGCC2_CFLAGS="-O0 -g3 -fno-omit-frame-pointer" ../srcdir/configure
--disable-nls --enable-version-specific-runtime-libs --enable-dwarf2
--with-cpu=pentium3 --with-arch=pentium3 --with-system-zlib --disable-shared
--prefix=/home/4/wilx --enable-languages=c,c++ --disable-sjlj-exceptions
--enable-shared=libstdc++ --enable-shared=libobjc --with-gc=zone


And these are examples where the flags are not used:

gcc -c   -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -DIN_GCC   -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes  -fno-common
-DHAVE_CONFIG_H -DGENERATOR_FILE -I/home/4/wilx/include   -I. -Ibuild
-I../../srcdir/gcc -I../../srcdir/gcc/build -I../../srcdir/gcc/../include
-I../../srcdir/gcc/../libcpp/include  \
 -o build/ggc-none.o ../../srcdir/gcc/ggc-none.c

gcc -c   -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -DIN_GCC   -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wold-style-definition -fno-common
-Wno-error  -DHAVE_CONFIG_H -I/home/4/wilx/include   -I. -I. -I../../srcdir/gcc
-I../../srcdir/gcc/. -I../../srcdir/gcc/../include
-I../../srcdir/gcc/../libcpp/include  c-parse.c -o c-parse.o

gcc -c   -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -DIN_GCC   -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wold-style-definition -fno-common
-DHAVE_CONFIG_H -I/home/4/wilx/include   -I. -I. -I../../srcdir/gcc
-I../../srcdir/gcc/. -I../../srcdir/gcc/../include
-I../../srcdir/gcc/../libcpp/include  ../../srcdir/gcc/tree-ssa-loop-manip.c -o
tree-ssa-loop-manip.o

These ignore the flags that I pass to both configure and make bootstrap. Though
it is not that bad because it compiles the stuff without optimization anyway.

The next one though uses -O2 despite the use of LIBGCC2_CFLAGS that you have
suggested:

./xgcc -B./ -B/home/4/wilx/i386-unknown-freebsd4.10/bin/ -isystem
/home/4/wilx/i386-unknown-freebsd4.10/include -isystem
/home/4/wilx/i386-unknown-freebsd4.10/sys-include
-L/home/4/wilx/tmp/gcc-head/objdir/gcc/../ld -O2  -DIN_GCC    -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include   -fPIC -pthread -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED  -I. -I. -I../../srcdir/gcc -I../../srcdir/gcc/.
-I../../srcdir/gcc/../include -I../../srcdir/gcc/../libcpp/include  -DL_ctzdi2
-c ../../srcdir/gcc/libgcc2.c -o libgcc/./_ctzdi2.o

The -O2 option is part of the gcc/Makefile.in file.


Vaclav Haisman



On Mon, 3 Jan 2005, pinskia at gcc dot gnu dot org wrote:

>
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2005-01-03 
> 15:26 -------
> LIBGCC2_CFLAGS changes the libgcc C flags.
>
> --
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |INVALID
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19234
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> You are on the CC list for the bug, or are watching someone who is.
>


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19234

Reply via email to