From: Bart Veer <bartv@ecoscentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: jifl@eCosCentric.com, ecos-maintainers@sourceware.org
Subject: Re: update ARM platform HALs
Date: Tue, 27 Jan 2009 11:35:00 -0000 [thread overview]
Message-ID: <pnvds1x9r7.fsf@delenn.bartv.net> (raw)
In-Reply-To: <497EED0F.7070501@dallaway.org.uk> (message from John Dallaway on Tue, 27 Jan 2009 11:16:31 +0000)
>>>>> "Jifl" == Jonathan Larmour <jifl@eCosCentric.com> writes:
Jifl> Actually there is one exception that should probably not be
Jifl> arm-eabi which is the AEB target, which is arm7di and so
Jifl> can't work with the new tools. Sorry I should have mentioned
Jifl> that yesterday Bart. Maybe it's worth putting that one back,
Jifl> but it may not be worth even that effort since no-one will
Jifl> be using it... I think it hasn't been sold for going on 10
Jifl> years now.
I'll revert the AEB to use arm-elf-gcc.
>>>>> "John" == John Dallaway <john@dallaway.org.uk> writes:
John> IIRC, Bart observed a SIGTRAP in libgcc (udivsi3?) when
John> running up eCos built with arm-eabi-gcc 4.3.2 on the ipaq
John> target. So perhaps users would be better off sticking with
John> arm-elf-gcc 3.2.1 for StrongARM? I'm not proposing that we
John> spend any further time investigating the problem, just
John> seeking clarification as to what we should recommend to
John> users.
That was back in October, the toolchain has been respun several times
since then. This is something to look at once the checkins are
complete and we have moved on to testing.
Also note that there are several ARM targets which completely fail to
build at the moment because of bitrot. And no doubt some number of
non-ARM targets will fail to build. Again, this should be looked at
after the checkins.
Bart
--
Bart Veer eCos Configuration Architect
eCosCentric Limited The eCos experts http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
next prev parent reply other threads:[~2009-01-27 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pny6wyx7p8.fsf@delenn.bartv.net>
2009-01-27 9:21 ` John Dallaway
2009-01-27 10:26 ` Jonathan Larmour
2009-01-27 10:33 ` Gary Thomas
2009-01-27 10:41 ` Jonathan Larmour
2009-01-27 11:16 ` John Dallaway
2009-01-27 11:35 ` Bart Veer [this message]
2009-01-27 12:10 ` Jonathan Larmour
2009-01-27 12:41 ` John Dallaway
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=pnvds1x9r7.fsf@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=ecos-maintainers@sourceware.org \
--cc=jifl@eCosCentric.com \
--cc=john@dallaway.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).