This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: ARM EABI port / static constructor priority removal

> Given that this is used in a number of places scattered all over the
> code, how do you propose to do this? What is you concept to ensure the
> constructors are called in the right order?

Ordering is preserved within one translation unit by C++ spec, just not
between multiple translation units.

BTW, I think the ARM EABI stuff will get fixed (CodeSourcery is looking at it
right now), I just think this is bad behavior to rely on in general.
It's not part of EABI and was somewhat reluctantly added to EABI GCC.

--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
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]