On Fri, 5 Feb 2016, Klaus Rudolph wrote:
What should happen on "illegal instruction" execution in simulavr:
1) stop simulavr with retrun code !=0 ( as yet imlemented )
2) act like running on a breakpoint, do not increment program counter
3) report a line on trace output
4) ....
0xFFFF should be a separate case from all other invalid instructions.
It seems to me that run-time configuration should include both the
effect on the simulatee and on the output text.
There is potential for a lot of output.
--
Michael henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards
_______________________________________________
Simulavr-devel mailing list
Simulavr-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/simulavr-devel
