public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: Bart Veer <bartv@ecoscentric.com>,  ecos-maintainers@sourceware.org
Subject: Re: update ARM platform HALs
Date: Tue, 27 Jan 2009 10:26:00 -0000	[thread overview]
Message-ID: <497EE13B.9020503@eCosCentric.com> (raw)
In-Reply-To: <497ED20D.3040709@dallaway.org.uk>

John Dallaway wrote:
> Hi Bart
> 
> Bart Veer wrote:
> 
> 
>>This patch updates all ARM platform HALs to use arm-eabi-gcc instead
>>of arm-elf-gcc, and removes -mno-short-load-words from platforms that
>>still used it.
> 
> 
> Thank you for the check-in.
> 
> The eCosCentric arm-eabi pre-built toolchains do not include StrongARM
> multi-libs. AFAIK, users who want to build eCos for these targets will
> therefore need to either build their own arm-eabi-gcc or revert to
> CYGBLD_GLOBAL_COMMAND_PREFIX == "arm-elf" and use the older arm-elf-gcc
> 3.2.1. Can you please let me know what the intention is here so I can
> mention this in the eCos 3.0 release notes?

This was discussed before IRL, and I believe until I hear to the contrary 
that strongarm should probably still work. It just won't be perfectly 
optimal as it will fall back to the arm7tdmi multilib (the default); but 
now actually looking at GCC sources, I think it may have only a virtually 
perceptible effect even then.

Actually there is one exception that should probably not be arm-eabi which 
is the AEB target, which is arm7di and so can't work with the new tools. 
Sorry I should have mentioned that yesterday Bart. Maybe it's worth 
putting that one back, but it may not be worth even that effort since 
no-one will be using it... I think it hasn't been sold for going on 10 
years now.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------      Opinions==mine

  reply	other threads:[~2009-01-27 10:26 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 [this message]
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
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=497EE13B.9020503@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=bartv@ecoscentric.com \
    --cc=ecos-maintainers@sourceware.org \
    --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).