On Wednesday 09 November 2011 23:22:34 Graeme Russ wrote: > On Thu, Nov 10, 2011 at 3:13 PM, Mike Frysinger wrote: > > i was referring also to throwing away -mregparm=3 ... > > Yes, it does effect the code - It makes it ABI compliant like everyone > else (except ARM) :) I expect a code size increase (have not measured > it yet)
ABI compliance only matters at the boundaries. since u-boot is largely self- contained, we shouldn't be afraid to break internal ABI. > As I've stated, I really do not want arbitrary wrapper functions where > it is not obvious that they need to be updated if new code uses > previously unused (and unwrapped) libgcc functions (in particular if > there are new libgcc functions in the future which we can't wrap > todday anyway) > > Option a) is to remove regparm=3 > Option b) is to use private libgcc > Option c) is to use wrappers > > If this patch works, I'll look at the code impact and we can discuss > which option we take :) for the record, i'm not against a private libgcc. it just seems to me that the wrapper approach proposed by Gabe has the best pro/con ratio. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
