Searched hist:9960 (Results 1 - 4 of 4) sorted by relevance
| /gem5/src/sim/ | ||
| H A D | debug.hh | diff 9960:501c7384a5bc Fri Nov 01 11:56:00 EDT 2013 Andreas Hansson <andreas.hansson@arm.com> sim: Clarify the difference between tracing and debugging This patch changes the name the command-line options related to debug output to all start with "debug" rather than being a mix of that and "trace". It also makes it clear that the breakpoint time is specified in ticks and not in cycles. |
| H A D | debug.cc | diff 9960:501c7384a5bc Fri Nov 01 11:56:00 EDT 2013 Andreas Hansson <andreas.hansson@arm.com> sim: Clarify the difference between tracing and debugging This patch changes the name the command-line options related to debug output to all start with "debug" rather than being a mix of that and "trace". It also makes it clear that the breakpoint time is specified in ticks and not in cycles. |
| /gem5/src/python/m5/ | ||
| H A D | debug.py | diff 9960:501c7384a5bc Fri Nov 01 11:56:00 EDT 2013 Andreas Hansson <andreas.hansson@arm.com> sim: Clarify the difference between tracing and debugging This patch changes the name the command-line options related to debug output to all start with "debug" rather than being a mix of that and "trace". It also makes it clear that the breakpoint time is specified in ticks and not in cycles. |
| H A D | main.py | diff 9960:501c7384a5bc Fri Nov 01 11:56:00 EDT 2013 Andreas Hansson <andreas.hansson@arm.com> sim: Clarify the difference between tracing and debugging This patch changes the name the command-line options related to debug output to all start with "debug" rather than being a mix of that and "trace". It also makes it clear that the breakpoint time is specified in ticks and not in cycles. |
Completed in 33 milliseconds