From: Nick Thompson <nick.thompson@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building for da830 fails
Date: Tue, 11 May 2010 09:59:16 +0100 [thread overview]
Message-ID: <4BE91C64.9050402@ge.com> (raw)
In-Reply-To: <20100510211709.DCEBBC67D4E@gemini.denx.de>
On 10/05/10 22:17, Wolfgang Denk wrote:
> In message <4BE43218.2060209@freescale.com> you wrote:
>> which means that in order to support support printing 64-bit numbers on ARM,
>> we might need to completely rewrite print_size() to avoid division on 64-bit
>> numbers.
>
> This actually makes little sense to me. Avoiding this here will just
> make the problem pop up somewhare else later.
True, but the extra library (and abi workaround) bloat is not necessary in
this particular case.
The proper fix is to either insist on a toolchain that supports 64bit divides,
or avoid using features not available in all toolchains that you wish to support.
In the later case, rewriting the function would be a good idea wouldn't it?
The eabi stub you submitted is only good as long as C++ and exceptions are not
used by U-Boot. Exceptions in particular are a powerful way to clean up error
handling code - can we ever say never?
Regards,
Nick.
next prev parent reply other threads:[~2010-05-11 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 11:57 [U-Boot] Building for da830 fails Sudhakar Rajashekhara
2010-05-07 14:14 ` Nick Thompson
2010-05-07 15:02 ` Nick Thompson
2010-05-07 15:09 ` Timur Tabi
2010-05-10 21:03 ` Wolfgang Denk
2010-05-07 15:14 ` Timur Tabi
2010-05-07 15:10 ` Wolfgang Denk
2010-05-07 15:21 ` Scott McNutt
2010-05-07 15:30 ` Timur Tabi
2010-05-10 10:39 ` Nick Thompson
2010-05-10 21:17 ` Wolfgang Denk
2010-05-11 8:59 ` Nick Thompson [this message]
2010-05-11 10:39 ` Wolfgang Denk
2010-05-11 11:30 ` Nick Thompson
2010-05-11 12:39 ` Scott McNutt
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=4BE91C64.9050402@ge.com \
--to=nick.thompson@ge.com \
--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