> Yes, Linux should definitely be compiled with -ffreestanding,
> it isn't a hosted application after all ;-)
We tried it some time ago and it caused problems so it was dropped
again
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Nope. The builtins not only vary between gcc versions, but they
also
have a nasty tendency to generate calls to library functions,
sometimes
libgcc functions. Hence -ffreestanding.
-ffreestanding will still generate calls to libgcc functions.
-ffreestanding doesn't disable _all_ of the C l
Segher Boessenkool wrote:
>> Nope. The builtins not only vary between gcc versions, but they also
>> have a nasty tendency to generate calls to library functions, sometimes
>> libgcc functions. Hence -ffreestanding.
>
> -ffreestanding will still generate calls to libgcc functions.
> -ffreestandi
Nope. The builtins not only vary between gcc versions, but they also
have a nasty tendency to generate calls to library functions,
sometimes
libgcc functions. Hence -ffreestanding.
-ffreestanding will still generate calls to libgcc functions.
-ffreestanding doesn't disable _all_ of the C li
Jan Engelhardt wrote:
> On Jul 9 2007 19:51, H. Peter Anvin wrote:
>> strcmp(), memcpy(), memset(), as well as routines to copy to and from
>> other segments (as pointed to by fs and gs).
>
> I wonder, strcmp() is the only one not done in assembler.
> Is there a particular reason? (Or the other wa
On Jul 9 2007 19:51, H. Peter Anvin wrote:
>
>strcmp(), memcpy(), memset(), as well as routines to copy to and from
>other segments (as pointed to by fs and gs).
I wonder, strcmp() is the only one not done in assembler.
Is there a particular reason? (Or the other way around, why
is memcpy/memset
6 matches
Mail list logo
