changeset e39a9c0493ad in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=e39a9c0493ad
description:
Mem: Use sysconf to get the page size instead of the PAGE_SIZE macro.
diffstat:
src/mem/physical.cc | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diffs (12
= Statistics differences =*
build/ALPHA_SE/tests/opt/quick/00.hello/alpha/tru64/simple-timing-ruby passed.
* build/ALPHA_SE/tests/opt/quick/60.rubytest/alpha/linux/rubytest-ruby
passed.
= Statistics differences =*
Hi,
I'm trying to call a global function implemented in C++ from a function in the
Python __init__.py file, how can I do that? Is that a good example that I can
follow?
Thanks,
William
-Original Message-
From: gem5-dev-boun...@m5sim.org [mailto:gem5-dev-boun...@m5sim.org] On Behalf
I'm trying to call a global function implemented in C++ from a function in
the Python __init__.py file, how can I do that? Is that a good example that I
can follow?
Just add your function foo() to src/python/swig/core.i and then you
can access it from m5.internal.core.foo()
Most of the
On Wed, 8 Jun 2011, Jack Harvard wrote:
When you declare your function private, you can't use instance.function() to
access it. Is it generating a compile time error?
On 8 Jun 2011, at 00:31, Nilay Vaish wrote:
Consider the following class declarations --
class A
{
public:
virtual void
On 8 Jun 2011, at 19:09, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
When you declare your function private, you can't use instance.function() to
access it. Is it generating a compile time error?
On 8 Jun 2011, at 00:31, Nilay Vaish wrote:
Consider the following class
Why not just let TraceFlags be interpreted as DebugFlags, so TraceFlags still
works for users.
For better or worse, I renamed trace flags to debug flags and I should
have changed the name of TraceFlags to DebugFlags when I did that, so
this was just correcting that and removing an
On Wed, 8 Jun 2011, Jack Harvard wrote:
On 8 Jun 2011, at 19:09, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
When you declare your function private, you can't use instance.function() to
access it. Is it generating a compile time error?
On 8 Jun 2011, at 00:31, Nilay Vaish
On 8 Jun 2011, at 23:28, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
On 8 Jun 2011, at 19:09, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
When you declare your function private, you can't use instance.function()
to access it. Is it generating a
On Wed, 8 Jun 2011, Jack Harvard wrote:
On 8 Jun 2011, at 23:28, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
On 8 Jun 2011, at 19:09, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
When you declare your function private, you can't use instance.function() to
On 9 Jun 2011, at 00:10, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
On 8 Jun 2011, at 23:28, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
On 8 Jun 2011, at 19:09, Nilay Vaish wrote:
On Wed, 8 Jun 2011, Jack Harvard wrote:
When you declare your
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/684/#review1301
---
Ship it!
This looks fine to me. I assume that if a controller doesn't
On 2011-06-08 17:11:26, Brad Beckmann wrote:
This looks fine to me. I assume that if a controller doesn't include a
setPermission or getPermission function, the compiler error message is the
same as when a controller doesn't specify a getState function. Correct?
Currently SLICC does
changeset 30daf1dd5c91 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=30daf1dd5c91
description:
Ruby: Correctly set access permissions for directory entries
The access permissions for the directory entries are not being set
correctly.
This is because
What do people (mostly Nate) think about having a single header file for all
debug flags?
Instead of #include debug/MyFlag.hh for every flag you want in a DPRINTF,
you could say #include debug/debugflags.hh and that would cover all the
debug flags available for DPRINTF.
Would that (the old way?)
What do people (mostly Nate) think about having a single header file for all
debug flags?
Instead of #include debug/MyFlag.hh for every flag you want in a DPRINTF,
you could say #include debug/debugflags.hh and that would cover all the
debug flags available for DPRINTF.
Would that (the old
Oh, and I forgot. Compound flags generate a header file as well.
debug/O3CPUAll.hh for example would have all of the flags that
O3CPUAll covers
On Wed, Jun 8, 2011 at 9:40 PM, nathan binkert n...@binkert.org wrote:
What do people (mostly Nate) think about having a single header file for all
Well, I guess the recompilation tradeoff is worth the temporary annoyance of
adding the specific debug flag header file everywhere.
I'm also hoping that the new changes will allow us to eventually make
compound flags of compound flags.
On Thu, Jun 9, 2011 at 12:42 AM, nathan binkert
changeset 77d12d8f7971 in /z/repo/gem5
details: http://repo.gem5.org/gem5?cmd=changeset;node=77d12d8f7971
description:
sparc: compilation fixes for inorder
Add a few constants and functions that the InOrder model wants for
SPARC.
* * *
sparc: add eaComp function
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/738/
---
Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/739/
---
Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt, and Nathan
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/738/#review1303
---
I think you missed some (maybe just one) version of PC state defined in
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/739/#review1304
---
Ship it!
- Gabe
On 2011-06-08 22:48:14, Korey Sewell wrote:
23 matches
Mail list logo
