re: Understanding the classical model for linking: Taking symbols along for the ride

I don't get why you need __fltused.  I thought that something like 1.2 + 3.4 gets compiled into something like __fltadd(1.2, 3.4).  Then you can resolve __fltadd instead of a bogus symbol like __fltused.