The current w11a implementation has several deficits in the handling of traps and interrupts which lead to non-conforming behavior when multiple trap, fault and interrupt conditions occur simultaneously, for example
bad stack frame when IOT trigger stack violation (TCK-003)
bad stack frame when interrupt triggers stack violation (TCK-004)
no yellow stack trap when jsr triggers a stack violation (TCK-006)
no odd address trap when EMT is executed with odd SP (TCK-007)
no yellow stack abort for mov (sp),(sp) (TCK-028)
These situations never occur during the execution of operation systems, and in case they do, the operating system will crash anyway. Thus there is no impact in normal usage, but diagnostics programs do complain. Will be fixed in an upcoming release.
_originally filed as issue w11aV0.50-1 and TCK-003,004,006,007,028 dated 2008-04-18 to 2009-05-03
The current w11a implementation has several deficits in the handling of traps and interrupts which lead to non-conforming behavior when multiple trap, fault and interrupt conditions occur simultaneously, for example
IOT
trigger stack violation (TCK-003)jsr
triggers a stack violation (TCK-006)EMT
is executed with oddSP
(TCK-007)mov (sp),(sp)
(TCK-028)These situations never occur during the execution of operation systems, and in case they do, the operating system will crash anyway. Thus there is no impact in normal usage, but diagnostics programs do complain. Will be fixed in an upcoming release.
_originally filed as issue w11aV0.50-1 and TCK-003,004,006,007,028 dated 2008-04-18 to 2009-05-03