public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@cygnus.co.uk>
To: alex@clockwork.freeserve.co.uk
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: CPU Ports for eCos
Date: Wed, 28 Apr 1999 04:17:00 -0000	[thread overview]
Message-ID: <199904281116.MAA32569@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <00f201be90f1$50c61730$63a1883e@plath.Workgroup>

>>>>> "Alex" == alex  <alex@clockwork.freeserve.co.uk> writes:

    >> Since
    >> eCos makes use of some compiler facilities that are tied to ELF

    Alex> Was that a good idea ?

In the medium to long term, yes. Technically ELF is superior to older
object formats such as a.out and COFF, it makes it much easier to
implement facilities such as constructor priority ordering and
selective linking. I believe that just about every new toolchain port
involves ELF as either the only object format or the preferred one.
Older toolchains may get updated because of user demand, partly
because of eCos but also because other systems like Linux use ELF.

In the short term there will be some targets where the ELF dependency
makes an eCos port more difficult. This is unfortunate, but the long
term advantages outweigh this.

Bart Veer // eCos net maintainer

  reply	other threads:[~1999-04-28  4:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-27 14:02 alex
1999-04-28  4:17 ` Bart Veer [this message]
1999-04-28  8:00   ` Jonathan Larmour
1999-04-28 12:04     ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
1999-04-23 13:41 [ECOS] " Nelson, Charles
1999-04-26  6:50 ` [ECOS] " Bart Veer
1999-04-28  6:41   ` Fernando D. Mato Mira
1999-04-28  7:10     ` Bart Veer
1999-04-28  8:52       ` Fernando D. Mato Mira
1999-04-28 11:48         ` Bart Veer
1999-04-28 12:17           ` Stan Shebs

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=199904281116.MAA32569@sheesh.cygnus.co.uk \
    --to=bartv@cygnus.co.uk \
    --cc=alex@clockwork.freeserve.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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).