Re: [PATCH 03/18] Set -msoft-float and assembler target options in the bootwrapper.

[Scott Wood <scottwood@freescale.com>]

Segher Boessenkool wrote:
>> Without -msoft-float, floating point state saving code can be executed
>> (at least with certain buggy versions of GCC, which don't clear bit  6 of
>> CR before calling a varargs function with no varargs parameters).
> 
> 
> I have a hard time understanding what this means.  Can you
> elaborate please?

The PowerPC ABI uses bit 6 of CR to indicate to a varargs function 
whether one (or more) of the varargs parameters is floating point.  This 
is used (among other things) by the varargs function to determine 
whether to save a floating point context.  Normally, GCC will clear the 
bit when calling a vararg function with integer-only parameters, but at 
least some versions (I saw it on 3.4.3) will not touch the bit at all 
when the varargs list is empty.

Since the functions in string.S use cr1 (which contains bit 6), this 
caused a fault on e500 (which doesn't have a normal floating point unit) 
when I called strcmp() followed by printf() of a bare string with no 
other arguments.

>>  AFLAGS += $(cpu-as-y)
>>  CFLAGS += $(cpu-as-y)
>> +export cpu-as-y
> 
> 
> Maybe it would be better to export CFLAGS instead (on the
> other hand, you might have to cut out some options from it
> for 32-bit compiles, dunno).

That'd also bring in the normal Linux headers, which the bootwrapper 
appears to be trying to avoid.

-Scott