From: "Chris Zimman" <czimman@bloomberg.com>
To: <ecos-discuss@sourceware.org>
Subject: [ECOS] ARM EABI port / static constructor priority removal
Date: Wed, 26 Mar 2008 18:06:00 -0000 [thread overview]
Message-ID: <F31C1582037F5041B0CD525FD870AE6A774244@ny2545.corp.bloomberg.com> (raw)
I have a nearly working port of eCos for the Broadcom BCM5890 that also
includes ARM EABI (arm-none-eabi-gcc) support. The idea is that people
should be able to build eCos with a supported toolchain (aka CodeSourcery)
(and perhaps at some point ADS). Redboot builds and runs fine under EABI now
(at least on this target, but I suspect it will be OK on other ARM targets as
well).
One of the things that's holding it up is the use of
__attribute__(init_priority(_pri_))) because there appears to be an issue (I
hesitate to call this a bug until it's further understood) where 'ld -r'
combines __init_array entry ordering when creating extras.o When you link
the resulting target images, the static constructor ordering gets messed up a
little bit, and of consequently things don't work right.
Anyhow -- one of the possible solutions that came out of this was to remove
the requirement for multiple translation unit static constructor ordering.
It's a GNU only extension and generally not considered good behavior.
It's a big change, but that by itself is not a good reason not to do it. Any
thoughts?
BTW, this ARM tree has a lot of general improvements. It includes support
for ARM processors that don't have the vector tables at 0x0, has a bunch of
additional ARM9 helper routines, low power sleep in the idle loop, etc.
--Chris
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2008-03-26 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 18:06 Chris Zimman [this message]
2008-03-26 18:09 ` Andrew Lunn
2008-03-26 18:18 ` Chris Zimman
2008-03-26 18:25 ` Andrew Lunn
2008-03-26 18:32 ` Chris Zimman
2008-03-26 18:38 ` Andrew Lunn
2008-03-26 18:42 ` Chris Zimman
2008-03-26 18:56 ` Andrew Lunn
2008-03-26 19:10 ` Chris Zimman
2008-04-02 14:20 ` Jonathan Larmour
2008-04-02 14:52 ` Chris Zimman
2008-03-26 20:47 ` Fabian Scheler
2008-03-27 1:53 ` Chris Zimman
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=F31C1582037F5041B0CD525FD870AE6A774244@ny2545.corp.bloomberg.com \
--to=czimman@bloomberg.com \
--cc=ecos-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).