From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] x86: Do no use reparm as it break libgcc linkage
Date: Thu, 10 Nov 2011 20:40:41 -0500 [thread overview]
Message-ID: <201111102040.43303.vapier@gentoo.org> (raw)
In-Reply-To: <CALButCLvLDVU+FuUJcVRgk0kE8d37vGLW0ZfjwebTMcpCPHq+w@mail.gmail.com>
On Thursday 10 November 2011 20:23:49 Graeme Russ wrote:
> On Fri, Nov 11, 2011 at 11:23 AM, Mike Frysinger wrote:
> > On Thursday 10 November 2011 17:53:06 Graeme Russ wrote:
> >> Now if we use USE_PRIVATE_LIBGCC, unimplemented libgcc functions will
> >> result in link errors, so using an unimplemented libgcc will be obvious
> >> at build time - It may lead to a posting on the mailing list, but at
> >> least we won't have latent libgcc related bugs in-the-wild.
> >
> > perhaps x86 should be setting PLATFORM_LIBGCC to nothing all the time.
> > the funcs Gabe wants to wrap are 64bit operations. u-boot should not be
> > doing 64- bit operations. that's why we have do_div().
>
> Remember that there was a lot of discussion regarding the timer API that
> pointed towards using 64-bit counters for all arches. We cannot take it
> as gospel that 64-bit operations will never be used in U-Boot. Some people
> may have a need for this as part of hardware init.
Linux has no problem doing 64bit timers without 64bit mul/div. i don't see
how u-boot could possibly be more special than Linux.
-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/4ac00f1d/attachment.pgp
next prev parent reply other threads:[~2011-11-11 1:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 9:27 [U-Boot] [PATCH] [x86] Wrap small helper functions from libgcc to avoid an ABI mismatch Gabe Black
2011-11-08 13:33 ` Mike Frysinger
2011-11-08 22:27 ` Gabe Black
2011-11-08 22:34 ` [U-Boot] [PATCH v2] x86: " Gabe Black
2011-11-08 23:14 ` Graeme Russ
2011-11-09 4:49 ` Mike Frysinger
2011-11-09 3:57 ` Graeme Russ
2011-11-09 5:34 ` Mike Frysinger
2011-11-17 9:01 ` [U-Boot] [PATCH v3] " Gabe Black
2011-11-17 9:13 ` Gabe Black
2011-11-30 11:03 ` Graeme Russ
2011-11-09 3:05 ` [U-Boot] [PATCH v2] " Graeme Russ
2011-11-09 10:32 ` [U-Boot] [RFC] x86: Do no use reparm as it break libgcc linkage Graeme Russ
2011-11-09 17:12 ` Mike Frysinger
2011-11-09 21:42 ` Graeme Russ
2011-11-10 4:13 ` Mike Frysinger
2011-11-10 4:22 ` Graeme Russ
2011-11-10 5:10 ` Graeme Russ
2011-11-10 17:15 ` Mike Frysinger
2011-11-10 22:53 ` Graeme Russ
2011-11-11 0:23 ` Mike Frysinger
2011-11-11 1:23 ` Graeme Russ
2011-11-11 1:40 ` Mike Frysinger [this message]
2011-11-11 1:51 ` Graeme Russ
2011-11-11 1:55 ` Mike Frysinger
2011-11-11 1:59 ` Graeme Russ
2011-11-11 2:10 ` Gabe Black
2011-11-11 2:22 ` Graeme Russ
2011-11-11 2:41 ` Gabe Black
2011-11-11 4:49 ` Graeme Russ
2011-11-11 5:04 ` Mike Frysinger
2011-11-11 5:16 ` Graeme Russ
2011-11-11 16:24 ` Mike Frysinger
2011-11-11 2:44 ` Mike Frysinger
2011-11-11 19:59 ` Scott Wood
2011-11-16 23:00 ` Graeme Russ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201111102040.43303.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox