Powerpc IRQ handling breaks strict EABI compliance

[Sergei Organov]

Joel Sherrill <joel.sherrill at oarcorp.com> writes:

[...]

> I agree with your analysis. The r2/r13 init needs to happen much earlier
> than constructors can be executed.
> 
> So the simplest solution (to me anyway) is:
> 
>   + bsp assembly startup initializes r2/r13 possibly using common code
>     derived from __eabi without the call to _init.
>   + call _init from _Threaad_Handler
> 
> Longer term, we can switch the toolset from non-EABI to EABI if that is
> desirable.

I also think this is the simplest solution. The only question remained is if
the __eabi() is GPLed, and if so, if the "common code derived from __eabi"
could be put into RTEMS ;-)

-- 
Sergei.