2) The formatting of the results are slightly different, so the
'expect' scripts fail:
"exit(00000000)" vs "exit(0)"
"report(0x00000009);" vs "report (0x00000009);" (note the extra space)
I guess ORPSoCV2 would be easier to fix, as there are less tests cases
to amend.
Please find attached a patch to do that (it's for the ORPSoCV2 repository).
Regards,
R. Diez
Index: bench/verilog/or1200_monitor.v
===================================================================
--- bench/verilog/or1200_monitor.v (Revision 783)
+++ bench/verilog/or1200_monitor.v (Arbeitskopie)
@@ -372,7 +372,9 @@
get_gpr(3, r3);
$fdisplay(fgeneral, "%t: l.nop exit (%h)", $time, r3);
`ifdef OR1200_MONITOR_VERBOSE_NOPS
- $display("exit(%h)",r3);
+ // Note that the 'expect' scripts in or1ksim's test suite look for
strings
+ // like "exit(1)", therefore something like "exit( 1)" would fail.
+ $display("exit(%0d)",r3);
`endif
$finish;
end
@@ -385,7 +387,10 @@
get_gpr(3, r3);
$fdisplay(fgeneral, "%t: l.nop report (0x%h)", $time, r3);
`ifdef OR1200_MONITOR_VERBOSE_NOPS
- $display("report (0x%h);", r3);
+ // Note that the 'expect' scripts in or1ksim's test suite look for
strings
+ // like "report(0x7ffffffe);", therefore something like "report
(0x7ffffffe);"
+ // (note the extra space character) would fail.
+ $display("report(0x%h);", r3);
`endif
end
// simulation printfs (l.nop 3)
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc
