ERC32 Ada
Prev	Chapter 2. Implementation-Defined Characteristics	Next

2.11. Appendix C: Systems Programming

The information in this section relates to Annex M paragraphs ?? to ??.

Q: M.(81)
Q: M.(82)
Q: M.(83)
Q: M.(84)
Q: M.(85)
Q: M.(86)
Q: M.(87)
Q: M.(88)
Q: M.(89)

Q: M.(81)

Support for access to machine instructions. See C.1(1).

A: See documentation in file s-maccod.ads in the distributed library.

Q: M.(82)

Implementation-defined aspects of access to machine operations. See C.1(9).

A: See documentation in file s-maccod.ads in the distributed library.

Q: M.(83)

Implementation-defined aspects of interrupts. See C.3(2).

A: Interrupts are mapped to signals or conditions as appropriate. See definition of unit Ada.Interrupt_Names in source file a-intnam.ads for details on the interrupts supported on a particular target.

Q: M.(84)

Implementation-defined aspects of pre-elaboration. See C.4(13).

A: ERC32 Ada does not permit a partition to be restarted without reloading, except under control of the debugger.

Q: M.(85)

The semantics of pragma Discard_Names. See C.5(7).

A: Pragma Discard_Names is currently ignored.

Q: M.(86)

The result of the Task_Identification.Image attribute. See C.7.1(7).

A: This feature is not supported.

Q: M.(87)

The value of Current_Task when in a protected entry or interrupt handler. See C.7.1(17).

A: The value of Current_Task is always the address of the task control block of the current base level task. This task may be running or interrupted.

Q: M.(88)

The effect of calling Current_Task from an entry body or interrupt handler. See C.7.1(19).

A: The effect of calling Current_Task from an entry body or interrupt handler is to return the identification of the task currently executing the code.

Q: M.(89)

Implementation-defined aspects of Task_Attributes. See C.7.2(19).

A: There are no implementation-defined aspects of Task_Attributes.

Prev	Home	Next
Appendix B: Interface to Other Languages	Up	Appendix D: Real-Time Systems