[RTEMS Project] #2692: User extensions execution order must be clarified

[RTEMS trac]

#2692: User extensions execution order must be clarified
-----------------------------+------------------------------
 Reporter:  sebastian.huber  |       Owner:  sebastian.huber
     Type:  defect           |      Status:  new
 Priority:  high             |   Milestone:  4.12
Component:  cpukit           |     Version:  4.11
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+------------------------------

Comment (by Sebastian Huber <sebastian.huber@…>):

 In [changeset:"6f6da82ca0b57ed1c42050f8103c2ea2adb3d3e2/rtems"]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="6f6da82ca0b57ed1c42050f8103c2ea2adb3d3e2"
 score: Fix user extensions order

 Use forward and reverse order for initial and dynamic extensions.  This
 is the behaviour documented in the C Users Guide.  Change thread
 terminate order to backward to be in line with the thread delete order.
 Change fatal error order to forward to ensure that initial extensions
 are called first due the peculiar execution context of fatal error
 extensions, see _Terminate() documentation.

 Update #2692.
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/2692#comment:3>
RTEMS Project <http://www.rtems.org/>
RTEMS Project