Re: Last chance handler on a PC

[Simon Wright <simon@pushface.org>]

Simon Wright <simon@pushface.org> writes:

> Niklas Holsti <niklas.holsti@tidorum.invalid> writes:
>
>> I had a similar elaboration problem some time ago in an embedded
>> application, where I wanted to set up some HW error-trap handlers that
>> I would like to be active also during elaboration, but I found no easy
>> way to ensure that the trap-handling package would be elaborated
>> before all other packages.
>
> Could you have used pragma Restrictions (No_Elaboration_Code); ?
>
> Or pragma No_Elaboration_Code_All --
>    This is a program unit pragma (there is also an equivalent aspect of
>    the same name) that establishes the restriction No_Elaboration_Code
>    for the current unit and any extended main source units (body and
>    subunits). It also has the effect of enforcing a transitive
>    application of this aspect, so that if any unit is implicitly or
>    explicitly with’ed by the current unit, it must also have the
>    No_Elaboration_Code_All aspect set. It may be applied to package or
>    subprogram specs or their generic versions.
>
> (I've done this in Cortex GNAT RTS, so that I could write the startup
> code in Ada).

Sorry, that was stupid: you needed the package to have elaboration code
so that it could set up the error-trap handlers!