public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Chris Zimman" <czimman@bloomberg.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@sourceware.org>
Subject: RE: [ECOS] ARM EABI port / static constructor priority removal
Date: Wed, 26 Mar 2008 18:42:00 -0000	[thread overview]
Message-ID: <F31C1582037F5041B0CD525FD870AE6A774247@ny2545.corp.bloomberg.com> (raw)
In-Reply-To: <20080326183202.GC5705@lunn.ch>

> So back to my original question, what is your concept for replacing
> them with something else. How are you going to ensure things happen in
> the right order.

One possibility is to put them all in one translation unit.  They are
constructed in the order that they appear, although that's kind of a big
kludge.
Another is to add explicit initialization calls to the various bits to invoke
the constructors at runtime.

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

  reply	other threads:[~2008-03-26 18:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 18:06 Chris Zimman
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 [this message]
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=F31C1582037F5041B0CD525FD870AE6A774247@ny2545.corp.bloomberg.com \
    --to=czimman@bloomberg.com \
    --cc=andrew@lunn.ch \
    --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).