Paolo Bonzini <bonz...@gnu.org> writes:
>> yes, using += gets my behind this point, now in stage2.
>
> Grep finds:
>
> ./config/mcore/t-mcore:HOST_LIBGCC2_CFLAGS = -O3 -DNO_FLOATLIB_FIXUNSDFSI
> #-msifilter
> ./config/m32r/t-m32r:HOST_LIBGCC2_CFLAGS = -G 0
> ./config/t-rtems:HOST_LIBGCC2_CFLAGS =
> -I$(srcdir)/../newlib/libc/sys/rtems/include
> ./config/avr/t-avr:HOST_LIBGCC2_CFLAGS = -DDF=SF -Dinhibit_libc
> -mcall-prologues -Os
> ./config/h8300/t-h8300:HOST_LIBGCC2_CFLAGS = -DDF=SF
> ./config/lm32/t-elf:HOST_LIBGCC2_CFLAGS = -G 0 -msign-extend-enabled
> ./config/mmix/t-mmix:HOST_LIBGCC2_CFLAGS = -mlibfuncs -O2
> ./config/mips/t-elf:HOST_LIBGCC2_CFLAGS = -G 0
> ./config/picochip/t-picochip:HOST_LIBGCC2_CFLAGS = -DDF=SF -I../../includes/
> ./config/sh/t-sh:HOST_LIBGCC2_CFLAGS = -mieee
> ./config/c6x/t-elf:HOST_LIBGCC2_CFLAGS = -msdata=none
> ./config/t-openbsd-thread:HOST_LIBGCC2_CFLAGS=-pthread
> ./config/bfin/t-elf:HOST_LIBGCC2_CFLAGS = $(PICFLAG)
> ./config/stormy16/t-stormy16:HOST_LIBGCC2_CFLAGS = -O2
> ./config/t-vxworks:HOST_LIBGCC2_CFLAGS =
> ./config/arm/t-strongarm-elf:HOST_LIBGCC2_CFLAGS = -fno-inline
> ./config/arm/t-elf:HOST_LIBGCC2_CFLAGS = -fno-inline
> ./config/pdp11/t-pdp11:HOST_LIBGCC2_CFLAGS = -O2 -mfloat32
>
> Do you think all of them should be changed?
Not without detailed analysis: they were moved over from gcc/config this
way, but I seem to have made an ordering mistake.
Several of them are for embedded targets without PIC support, but others
might need to be changed. I'm undecided what's more risky:
* leave them as moved over, wait what breaks, and then change them,
* change them all now, and if something breaks, change them back with an
explanation why an override is necessary.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
