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

[Andrew Lunn <andrew at lunn dot ch>]

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

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?

    Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss