Messages in this thread | | | Date | Wed, 21 May 2008 10:52:34 +0300 | From | Adrian Bunk <> | Subject | -ffreestanding or not -ffreestanding |
| |
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 > version... >...
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.
cu Adrian
--
"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
| |