William Harrington wrote on 16-04-07 19:12: > Binaries, that link to libs that are optimized, will use the > optimized code the library provides. That is what was meant. Which > means if you optimize a library, problems could arise where > segmentation faults occur from that library and not from the binary > itself.
I.o.w. the consequences of optimization (both good and bad, but the latter should always be of overriding importance) of a libc build will trickle down into every binary that is later linked to that libc. And it's very hard to tell beforehand if and where an overly optimized libc will fail. Plus, with the same set of optimizations, compiler version x.y.z may yield a faultless libc, where compiler version x.y.z+1 might not, or vice versa. Which means: better safe than sorry. bjd -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
