On Mon, Nov 07, 2005 at 07:19:01AM -0800, Ulrich Drepper wrote: > Richard Guenther wrote: > > Also, libgcc > > does _not_ know the machine - it only knows the -march it was compiled > > for. Inlining and transparently handling different sub-architecture just > > does not play together well. > > Yes, libgcc doesn't know this. But the libgcc can be installed in the > correct place and the dynamic linker, which does in fact know what arch > is used, can make the decision. It's really pretty easy for those > platforms with sufficient flexibility. Use if cascades or indirect > jumps for the others, if necessary.
The only real problem with this is that it mandates use of shared libgcc for the routines in question... always. If they ever go into libgcc.a, we can't make sure we got the right copy. -- Daniel Jacobowitz CodeSourcery, LLC
