Thanks for getting these patches out, Brad.
On Thu, Jan 14, 2010 at 10:19 PM, Brad Beckmann brad.beckm...@amd.com wrote:
- These patches do not remove the old ruby config and rubymem files.
However, once these patches are checked in, those old files won't be needed.
Anyone have an opinion
- These patches do not remove the old ruby config and rubymem files.
However, once these patches are checked in, those old files won't be needed.
Anyone have an opinion on how long they would like those files to stick
around? I would like to delete them as soon as we can.
Why not
Unless there's ever a reason why a user would want to set this low bit
to something other than the log2 of the block size, then this value
should just be calculated in C++, in my opinion.
I would agree with this.
The reason it doesn't work is because math operations on proxy values
have to
I failed to mention earlier that the parameter is used in the protocol files so
it isn't just simple C++. However, it is simple enough to make SLICC generate
the correct C++ since RubySystem has static functions that provide the block
size bits. Once these functions are no longer static, the
The main reason not to delete the old config files now is libruby has yet to be
updated. I wanted to hear Derek and others opinion before I removed the files.
Brad
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] On
Behalf Of nathan binkert
Sent:
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic-ruby
passed.
*
