From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Thu, 10 Nov 2011 12:15:32 -0500 Subject: [U-Boot] [RFC] x86: Do no use reparm as it break libgcc linkage In-Reply-To: References: <1320834779-15460-1-git-send-email-graeme.russ@gmail.com> <201111092313.25335.vapier@gentoo.org> Message-ID: <201111101215.33554.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20111110/9683c94d/attachment.pgp