public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: taiyun@sunnorth.com.cn
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: eCos with arm eabi compiler
Date: Fri, 21 Sep 2007 16:04:00 -0000	[thread overview]
Message-ID: <46F3EB63.1080309@eCosCentric.com> (raw)
In-Reply-To: <OF85D24AD2.200A9EC6-ON48257354.0011E634-48257354.0011E63C@sunnorth.com.cn>

taiyun@sunnorth.com.cn wrote:
> 
> arm-eabi compiler's linker script has different sections from arm-elf
> compiler's, e.g: .ARM.extab, .ARM.exidx and .ARM.attributes 0, these 3
> sections are own in arm-eabi compiler. These sections should be added to
> arm.ld, aren't they? 

Yes they would want to be added.

> If so, there are 2 ways to achieve this goal. One is
> making direct changes to arm.ld and adding corresponding sections'
> definitions. The other is setting up a new arch-eabi directory in hal/arm,
> which is only for arm-eabi compiler. Which is the best?

Definitely the first is best, from what you describe. The changes are 
relatively small, so a whole new package is not required.

Obviously care will be required to preserve the behaviour of existing 
arm-elf toolchains.

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.
  >>>> Visit us on stand 810 at The Embedded Systems Show 2007, NEC <<<<
  >>>> Oct 17-18 Birmingham, UK http://www.edaexhibitions.com/ess/  <<<<
------["The best things in life aren't things."]------      Opinions==mine

      reply	other threads:[~2007-09-21 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12  3:15 taiyun
2007-09-21 16:04 ` Jonathan Larmour [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=46F3EB63.1080309@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=taiyun@sunnorth.com.cn \
    /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).