> On 2010-10-21 15:23:04, Brad Beckmann wrote:
> > src/mem/ruby/common/Debug.hh, line 231
> > <http://reviews.m5sim.org/r/277/diff/1/?file=4476#file4476line231>
> >
> >     I agree with Steve's point that adding "__PRETTY_FUNCTION__, __FILE__, 
> > __LINE__" to every Ruby DPRINTF call is too cumbersome and we either need 
> > to remove it or define a macro that does it automatically.  Nilay, I think 
> > I might have confused you during our previous email conversations.  We 
> > definitely want to automatically include the function name, file, and line 
> > number for the SLICC/.sm debug statements...I've found that feature very 
> > useful in the past.  However, I'm not sure we need it for the debug 
> > statements on the Ruby side.  Nilay, if I understand your changes to SLICC 
> > correctly and recall from our previous conversations on this topic, these 
> > old ruby DEBUG macros relied on the ostream operator<< overloading, 
> > correct? That is why you now have the conditional statements in the SLICC 
> > that generate the correct DPRINTF line depending on the type.  Am I 
> > understanding the issues correctly?  If so, I think your solution for the 
> > SLICC generation of DPRINTF statements loo
 ks good.  I just think that we need to clean up the Ruby DPRINTF statements.
> >

I will remove the function name, file name, line number from Ruby DPRINTF 
statements.


- Nilay


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/277/#review399
-----------------------------------------------------------


On 2010-10-19 17:30:48, Nilay Vaish wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.m5sim.org/r/277/
> -----------------------------------------------------------
> 
> (Updated 2010-10-19 17:30:48)
> 
> 
> Review request for Default and Ruby Reviewers.
> 
> 
> Summary
> -------
> 
> Ruby currently uses GEMS debug support with the enum character string map to 
> enable certain debug messages.  Meanwhile, M5 has debug print support that 
> works with scons. Compiling the m5.fast binary, the M5 debug statements are 
> removed, but the Ruby ones are not unless RUBY_DEBUG is not defined. This 
> patch moves Ruby to M5's debug print support.
> 
> 
> Diffs
> -----
> 
>   src/cpu/testers/rubytest/CheckTable.cc 956ac83b0a58 
>   src/mem/SConscript 956ac83b0a58 
>   src/mem/protocol/MESI_CMP_directory-L1cache.sm 956ac83b0a58 
>   src/mem/protocol/MESI_CMP_directory-L2cache.sm 956ac83b0a58 
>   src/mem/protocol/MESI_CMP_directory-dir.sm 956ac83b0a58 
>   src/mem/protocol/MI_example-cache.sm 956ac83b0a58 
>   src/mem/protocol/MI_example-dir.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_CMP_directory-L1cache.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_CMP_directory-L2cache.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_CMP_directory-dir.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_CMP_directory-perfectDir.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_CMP_token-L1cache.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_CMP_token-L2cache.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_CMP_token-dir.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_hammer-cache.sm 956ac83b0a58 
>   src/mem/protocol/MOESI_hammer-dir.sm 956ac83b0a58 
>   src/mem/protocol/RubySlicc_Exports.sm 956ac83b0a58 
>   src/mem/protocol/RubySlicc_MemControl.sm 956ac83b0a58 
>   src/mem/protocol/RubySlicc_Types.sm 956ac83b0a58 
>   src/mem/ruby/SConsopts 956ac83b0a58 
>   src/mem/ruby/buffers/MessageBuffer.cc 956ac83b0a58 
>   src/mem/ruby/common/Address.hh 956ac83b0a58 
>   src/mem/ruby/common/DataBlock.hh 956ac83b0a58 
>   src/mem/ruby/common/Debug.hh 956ac83b0a58 
>   src/mem/ruby/common/Debug.cc 956ac83b0a58 
>   src/mem/ruby/common/NetDest.hh 956ac83b0a58 
>   src/mem/ruby/common/NetDest.cc 956ac83b0a58 
>   src/mem/ruby/network/garnet/fixed-pipeline/NetworkInterface_d.cc 
> 956ac83b0a58 
>   src/mem/ruby/network/garnet/fixed-pipeline/Switch_d.cc 956ac83b0a58 
>   src/mem/ruby/network/garnet/flexible-pipeline/NetworkInterface.cc 
> 956ac83b0a58 
>   src/mem/ruby/network/garnet/flexible-pipeline/Router.cc 956ac83b0a58 
>   src/mem/ruby/network/simple/PerfectSwitch.cc 956ac83b0a58 
>   src/mem/ruby/network/simple/Throttle.cc 956ac83b0a58 
>   src/mem/ruby/network/simple/Topology.cc 956ac83b0a58 
>   src/mem/ruby/slicc_interface/Message.hh 956ac83b0a58 
>   src/mem/ruby/slicc_interface/NetworkMessage.hh 956ac83b0a58 
>   src/mem/ruby/storebuffer/storebuffer.cc 956ac83b0a58 
>   src/mem/ruby/system/CacheMemory.cc 956ac83b0a58 
>   src/mem/ruby/system/DirectoryMemory.cc 956ac83b0a58 
>   src/mem/ruby/system/SConscript 956ac83b0a58 
>   src/mem/ruby/system/SparseMemory.cc 956ac83b0a58 
>   src/mem/ruby/tester/RaceyPseudoThread.cc 956ac83b0a58 
>   src/mem/slicc/ast/FuncCallExprAST.py 956ac83b0a58 
>   src/mem/slicc/symbols/StateMachine.py 956ac83b0a58 
>   src/mem/slicc/symbols/Type.py 956ac83b0a58 
> 
> Diff: http://reviews.m5sim.org/r/277/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Nilay
> 
>

_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to