From: Markus Pietrek <maillist@fsforth.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot with gcc-3.3.2 and ARM926EJS Targets fails due to __udi
Date: Thu, 29 Jan 2004 09:37:25 +0100 [thread overview]
Message-ID: <200401290937.25064.maillist@fsforth.de> (raw)
In-Reply-To: <fc.004c4e48002071d73b9aca009ccdb13f.207378@rea.de>
Hello,
> your compiler wasn't built for a stand-alone target, otherwise
> it would have included a full implementation of __div0, __udivsi3 etc.
> However, there might be an easy solution to your problem, see below.
There is a full set already available in the gcc? But anyway, it makes not
much sense using two different gcc compilers. One for the bootloader, one for
applications. And with which one has the linux kernel to be compiled?
> The reason for the difference is the link order:
> For SMDK2410, __udivsi3 is needed by a module linked before libarm.a
> (in this case, cpu/arm920t/speed.c), whereas for NS9750 no module
> before or in libarm.a needs it; drivers/libdrivers.a is linked after
> libarm.a, so the linker won't go back to get __udivsi3 there and falls
> back to using libgcc.a, which is linked last.
Yes, of course. Now I see it. I'm needing the non-power 2 division only in the
serial driver for calculation the baudrate divisior. And libdrivers has been
after libarm :-(
> Please try the attached quick patch and let us know if it solves the
> problem (or if it breaks thing). Caveat - I haven't tried it myself
> yet!
Thank you, it works fine. Therefore, in the near future a new board and CPU
will be supported by U-Boot :-)
Bye,
--
Markus Pietrek
Kueferstrasse 8, D-79206 Breisach, Germany
FS Forth-Systeme GmbH
Phone: +49 (7667) 908 145, FAX +49 (7667) 908 221
next prev parent reply other threads:[~2004-01-29 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 14:24 [U-Boot-Users] U-Boot with gcc-3.3.2 and ARM926EJS Targets fails due to __udiv0 Markus Pietrek
2004-01-28 10:37 ` [U-Boot-Users] U-Boot with gcc-3.3.2 and ARM926EJS Targets fails due to __udi Anders Larsen
2004-01-28 16:55 ` Wolfgang Denk
2004-01-29 8:37 ` Markus Pietrek [this message]
2004-02-01 18:27 ` Robert Schwebel
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=200401290937.25064.maillist@fsforth.de \
--to=maillist@fsforth.de \
--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