From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org,
"Michael K. Edwards" <medwards.linux@gmail.com>
Subject: Re: softfloat calling conventions in ARM gcc 4.x
Date: Mon, 11 Dec 2006 09:42:28 +0000 [thread overview]
Message-ID: <1165830148.5633.9.camel@localhost.localdomain> (raw)
In-Reply-To: <f2b55d220612061129k102c45f1ye80c6197edfef72f@mail.gmail.com>
On Wed, 2006-12-06 at 11:29 -0800, Michael K. Edwards wrote:
> I've been using crosstool as a framework for building ARM linux
> cross-compile toolchains with a fair amount of success, but there are
> certainly some tricks and traps. OpenEmbedded toolchains have
> impressed some of the crosstool participants, and I'm starting to look
> at them now. I'm pleased to see that EABI support is stabilizing, and
> expect to use it for most ARM builds in the future. However, I
> anticipate needing to run existing OABI binaries on the system, and
> some of those have been built with soft FP.
>
> It seems that there have long been some patches needed for soft-float
> toolchains, which have not been applied to GCC upstream for good and
> sufficient reason. The patch at
> http://www.handhelds.org/hypermail/oe-commits/54/5483.html contains
> one variant of these changes for a gcc 4.2 snapshot.
Admittedly, the gcc 4.x OpenEmbedded toolchains have been developed
mainly by pulling together knowledge from other places. Our advantage
for toolchain development over others is that the resulting OE images
really stress toolchains so we've been likely to find bugs and then find
the fixes to address those bugs. We are a bit short of toolchain experts
working on OE atm though and I'm not sure we have anyone with the
knowledge to answer your questions. I could attempt some answers but I'm
not 100% sure so its perhaps best you check it out properly...
> I plan to actually test these things and report back to the
> OpenEmbedded, crossgcc, and linux-arm-toolchain lists. But even
> thorough testing is no substitute for a description of the theory of
> operations; so any comments from people who know what they are doing
> are welcome.
Please do report back. If you can see any problems with the toolchain,
comments, patches and other feedback is more than welcome.
Regards,
Richard
prev parent reply other threads:[~2006-12-11 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 19:29 softfloat calling conventions in ARM gcc 4.x Michael K. Edwards
2006-12-11 9:42 ` Richard Purdie [this message]
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=1165830148.5633.9.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=medwards.linux@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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