RE: [ECOS] ARM EABI port / static constructor priority removal

["Chris Zimman" <czimman@bloomberg.com>]

> just my two cents about that topic - the global objects we are talking
> about are singletons, right? So what about something like that
> 
> Cyg_Scheduler* theScheduler() {
>   static Cyg_Scheduler theScheduler;
>   return &theScheduler;
> }

That seems like a viable option.

> btw - I have no problem with the init-priority attribute. I believe
> that avoiding compiler dependencies is nearly as hard as to be
> processor independent. So, for the most OSes provided as source code
> the user is supposed to use a specific compiler and with eCos one is
> supposed to use gcc

eCos is by and large CPU independent.  Only a small part of it is processor
specific.  If you *have* to be compiler specific for some reason, fine.  But
I can't see a good reason to be just for the sake of it or because of design
choices that are fixable.

Prior to the ARM EABI work I am doing, you couldn't build CodeSourcery tool
chain either, so if you wanted a supported version of GCC w/ eCos you were
out of luck.  To me, that's a serious drawback for using eCos.  We ran into
internal compiler errors with GCC 3.4.4 and bad behavior in our application
when building with -O2 in some cases.

> It is also not possible to compile the linux kernel using the Microsoft
Compiler, is it?

One thing at a time ;)
 
--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