-ffreestanding or not -ffreestanding
From: Adrian Bunk
Date: Wed May 21 2008 - 03:54:57 EST
On Wed, May 21, 2008 at 02:12:07AM +0100, Al Viro wrote:
> Content-Length: 788
> Lines: 30
> Whether we sidestep it in init/main.c or not, such situations
> will arise again; compiler does generate calls of strcat()
> on optimizations, so we really ought to have an out-of-line
Can we try to get this sorted out properly instead of constantly
fiddling with it?
Currently we use -ffreestanding on some architectures and fix breakages
on the other architectures when they arise.
The options I see for getting this fixed properly are:
- use -ffreestanding on all architectures or
- don't use -ffreestanding on any architecture and move the string
functions (and perhaps other functions if required) out-of-line
I'd prefer the first option, but I know that not everyone agrees with me.
No matter which option we choose, if we get an agreement on this one
I can send patches for it.
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/