I think the reason those wouldn't be renamed is that you're only
outputing something you could put in a file (in the traditional sense)
if you're tracing. If you're turning on/off some other functionality
like a debug breakpoint you're not tracing, you're debugging. It gets a
little confusing, I th
changeset db269e704d07 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=db269e704d07
description:
NetworkTest: added sim_cycles parameter to the network tester.
The network tester terminates after injecting for sim_cycles
(default=1000), instead of having
Hey guys,
I wasn't sure what the intended outcome with tracing v. debugging was
going to be. It sounds like the move is to "debug" as a more general term,
though it will support all of the "trace" functionality. In that case, my
confusion arose from the naming of the flags. Since "trace-file"
changeset 0990d8c19b64 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=0990d8c19b64
description:
network: added Torus and Pt2Pt topologies
diffstat:
src/mem/ruby/network/topologies/Pt2Pt.py | 55 +
src/mem/ruby/network/topologies/SConscript |3 +-
s
> I was thinking og doing it since Nate is not around. I'll do it soon.
>> instance, "trace-flags", and "trace-file" are still accepted, but they
>> don't
>> do anything now. They should be eliminated from the message. We're also
>> missing the equivalent of "trace-start" and "trace-file". Do
Thanks for the response Nilay.
DPRINTF works, but I'm talking about say a "warn" or "warn_once" m5 debug
statement. Or even an "inform" or "panic". I guess error is similar to panic
(maybe it should be changed to use m5's panic?).
So the question is, if I want to add some other debug function, wh
Koreay, DPRINTF already works in sm files. Use RubySlicc as the flag. You
can also use error() and assert() functions which have the following
prototypes --
void error(std::string msg);
void assert(bool condition);
--
Nilay
On Fri, 6 May 2011, Korey Sewell wrote:
I guess I should rephrase t
Korey, I don't think there will be any change in the simulation
performance. I am not sure about stats.
Brad, were the stats updated after you made the change?
--
Nilay
On Fri, 6 May 2011, Korey Sewell wrote:
Nilay,
can you explain the impact of that bug in terms of simulation performance?
Joel, I have pushed in the patch the removes the options trace-help and
trace-flags. But trace-start and trace-file work as before. You can use
them in conjunction with debug-flags.
--
Nilay
On Fri, 6 May 2011, Nilay Vaish wrote:
I was thinking og doing it since Nate is not around. I'll do i
changeset a6363c870af6 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=a6363c870af6
description:
Trace: Remove the options trace-help and trace-flags
The options trace-help and trace-flags are no longer required. In there
place,
the options debug-help and
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linux/inorder-timing passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/linux/simp
11 matches
Mail list logo
