----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.m5sim.org/r/635/#review1103 -----------------------------------------------------------
src/mem/ruby/network/simple/PerfectSwitch.cc <http://reviews.m5sim.org/r/635/#comment1472> You are probably right here. No need to print out the time 2x. A slightly different scenario for DPRINTFRs though. src/mem/ruby/system/Sequencer.cc <http://reviews.m5sim.org/r/635/#comment1470> DPRINTFR doesnt print the tick, but DPRINTF does print the tick. curTick() is needed here. src/mem/ruby/system/Sequencer.cc <http://reviews.m5sim.org/r/635/#comment1471> Ditto about DPRINTFR which doesnt automatically print out the ticks for you. - Korey On 2011-04-05 11:19:26, Korey Sewell wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.m5sim.org/r/635/ > ----------------------------------------------------------- > > (Updated 2011-04-05 11:19:26) > > > Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and > Nathan Binkert. > > > Summary > ------- > > ruby: dbg: use system ticks instead of cycles > It's easier to debug simulations (find the exact point to rerun a trace) when > the output is in > the system ticks instead of the Ruby cycle time > > > Diffs > ----- > > src/mem/ruby/buffers/MessageBuffer.cc 54a65799e4c1 > src/mem/ruby/network/simple/PerfectSwitch.cc 54a65799e4c1 > src/mem/ruby/system/Sequencer.cc 54a65799e4c1 > src/mem/slicc/symbols/StateMachine.py 54a65799e4c1 > src/mem/slicc/symbols/Type.py 54a65799e4c1 > > Diff: http://reviews.m5sim.org/r/635/diff > > > Testing > ------- > > > Thanks, > > Korey > > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
