* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/o3-timing passed.
*
build/ALPHA_SE_MOESI_CMP_token/tests/opt/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token
passed.
*
Ok, there has been a lot of confusion about debug flags and trace
flags. I changed the way the flags stuff worked from a compile
perspective which required me to make changes throughout the tree, so
I took the opportunity to rename the trace flags to debug flags. The
idea behind the change was
So, I think part of the confusion is that there are two names now,
debug flags and trace flags, but they're different views of the same
mechanism (yes? no?) It seems like the --trace* options are like the
--debug* options, except their intended use is a subset of --debug*,
specifically
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/611/
---
(Updated 2011-06-01 18:59:16.473427)
Review request for Default.
Summary
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/611/
---
(Updated 2011-06-01 18:59:39.117342)
Review request for Default.
Summary
---
Hi.
I am currently using GEMS and Simics. So I care about whether the corresponding
codes are also updated in GEMS.
-Yongbing Huang
发件人： Nilay Vaish
发送时间： 2011-06-02 09:57:40
收件人： Nilay Vaish; Default; Brad Beckmann; Steve Reinhardt; Gabe Black
抄送：
主题： Re: [gem5-dev] Review Request:
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/723/
---
Review request for Default.
Summary
---
SLICC: Add a check function for State
I had posted a review request, it is not appropriate to respond to it with
these type of questions. These questions should be asked on gem5-users
list.
And now the answer to your question. We currently do not update GEMS code.
And I do not think that there is any plan to do so in future. In
On my phone, so I'll be brief, but just fixing the scons to be consistent
sounds good to me.
On Jun 1, 2011 6:55 PM, Gabriel Michael Black gbl...@eecs.umich.edu
wrote:
So, I think part of the confusion is that there are two names now,
debug flags and trace flags, but they're different views of
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/668/
---
(Updated 2011-06-01 21:27:23.466278)
Review request for Default, Ali Saidi, Gabe
Reviewboard didn't give me a chance to comment, but this is basically the
same as before except I now prompt for an input before modifying the
.hg/hgrc. The truly paranoid can hit ctrl-c and get out of there. I
thought it would be nice to get this in before the tutorial, since ideally
we'll have
OK, now that I'm at a keyboard: if we change the scons thing from
TraceFlag() to DebugFlag(), then there's one set of flags with one set
of names, it's all debug flags. Some (currently most) of them are
only used to control DPRINTFs, but they could be used for other
things, and the same flag
changeset aa00cee9abb1 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=aa00cee9abb1
description:
SimObject: allow modules in subclass definitions
In particular, this avoids crashing when you do
an import (like import pdb) inside a SimObject
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/668/#review1293
---
Ship it!
- Ali
On 2011-06-01 21:27:23, Steve Reinhardt wrote:
I'll post a diff to fix the SCons stuff very soon. Just compiling
stuff to make sure it works.
The biggest problem with two namespaces is that it's a lot of code to
manage to support both of them. The debug flags stuff is all over the
place: scons to generate the flags files, command line
15 matches
Mail list logo
