public inbox for
 help / color / mirror / Atom feed
Subject: eCos with arm eabi compiler
Date: Wed, 12 Sep 2007 03:15:00 -0000	[thread overview]
Message-ID: <> (raw)

Dear all:
We are now porting eCos kernel to our platform, EVB named
spaca556g(arm926ej-s). We choose a gcc4.2 eabi
compiler( The
reason of choosing this compiler is that an EABI compiler can be completely
compatible with ARM RealView libraries. With this arm-eabi compiler,
libraries built from realview can be used.
But there are some problems using this eabi compiler. Because of different
constructing method between arm-elf compiler and eabi compiler,
constructors of global instances can't be invoked automatically when using
the eabi compiler. As a result, we have to make changes to arm.ld and
hal_misc.c files.

NOTE: arm-elf compiler use .ctor section and 2 labels(__CTOR_LIST__,
__CTOR_END__) to invoke constructors, BUT arm-eabi compiler use .init_array
section and lables(__init_array_start, __init_array_end)

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? 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?

Taylor Wang
Special Manager,
  Product Development Div I.,
  Bejing Sunnorth Electronic Technology Co.,LTD
Tel: 62981668 Ext.2302
Fax: 62985972

             reply	other threads:[~2007-09-12  3:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12  3:15 taiyun [this message]
2007-09-21 16:04 ` Jonathan Larmour

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).