Output value not assigned

[Daniel Páscoa]

The Software Document Design (starting on page 181) specifies that there should be two outputs, but the RTEMS_UNSATISFIED is not returned by the function. The only failure detected may be due to the assert function, but the rtems_status_code isn't the returned value. Ensure all output values specified in the SDD are returned.

Additional Notes:
From code analysis and from objdumping the librtemsbsp.a library it can be observed that the asserts() currently do nothing: they are translated to #define _Assert( _e ) ( ( void ) 0 ) unless RTEMS_DEBUG or RTEMS_STATIC_ANALYSIS are defined, which in a release environment target are not defined. Since in the documentation it says that it can return RTEMS_UNSATISFIED or RTEMS_SUCCESSFUL either the documentation is wrong, or the code is not correctly implemented.

This ticket was raised as an outcome of the Independent SW Verification and Validation (ISVV) for ESA-promoted RTEMS SMP Qualification Data Packs (​https://rtems-qual.io.esa.int). The original ISVV reference for this issue is RTEMS-SMP-CODE-VER-032.

File list:
bsps\sparc\leon3\start\eirq.c

bsp_interrupt_is_pending (line 106)
bsp_interrupt_raise (line 127)
bsp_interrupt_clear (line 185)
bsp_interrupt_vector_enable (line 270)
bsp_interrupt_vector_disable (line 299)

[Sebastian Huber <sebastian.huber@…>]

In [changeset:"519e288a9615ccea12f528c9b49e633baab24c1e/rtems" 519e288/rtems]:

Error: Processor CommitTicketReference failed

/data/trac/repo/rtems.git does not appear to be a Git repository.