From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx5: Correct a warning in clock.c
Date: Sun, 20 Nov 2011 00:31:05 -0500 [thread overview]
Message-ID: <201111200031.06719.vapier@gentoo.org> (raw)
In-Reply-To: <CAPnjgZ2RY0rmGxBFMcUb6uMH6OWRuPyy1O4KK-sMmLqjhGf6zg@mail.gmail.com>
On Sunday 20 November 2011 00:08:05 Simon Glass wrote:
> On Fri, Nov 18, 2011 at 11:53 AM, Mike Frysinger wrote:
> > On Friday 18 November 2011 12:20:02 Stefano Babic wrote:
> >> On 11/05/2011 03:25 PM, Simon Glass wrote:
> >> > This corects the warning below, obtained with my gcc 4.6 compiler.
> >> >
> >> > arch/arm/cpu/armv7/mx5/libmx5.o: In function `decode_pll':
> >> > arch/arm/cpu/armv7/mx5/clock.c:94: undefined reference to
> >> > `__aeabi_uldivmod'
> >>
> >> I do not see the issue you reported.
> >
> > are you using PRIVATE LIBGCC ?
>
> Yes, perhaps as a side-effect of the buildall script...
by design. some arm boards want big endian, some want little. using private
allows using of just one gcc.
> Since a recent ARM patch to support widen divide was rejected, I
> assume that we should use do_div() in these cases?
yes, as it involves a 64bit in the division.
-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/20111120/8993ed44/attachment.pgp>
next prev parent reply other threads:[~2011-11-20 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 14:25 [U-Boot] [PATCH] mx5: Correct a warning in clock.c Simon Glass
2011-11-18 17:20 ` Stefano Babic
2011-11-18 19:53 ` Mike Frysinger
2011-11-20 5:08 ` Simon Glass
2011-11-20 5:31 ` Mike Frysinger [this message]
2011-11-20 5:43 ` Simon Glass
2011-11-21 11:04 ` Stefano Babic
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=201111200031.06719.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