[m5-dev] changeset in m5: X86: Decode three byte opcodes.

2009-08-18 Thread Gabe Black
changeset f0e4e63310e5 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=f0e4e63310e5 description: X86: Decode three byte opcodes. diffstat: 5 files changed, 164 insertions(+), 28 deletions(-) src/arch/x86/isa/decoder/decoder.isa| 20 ---

[m5-dev] changeset in m5: X86: Decode the immediate byte opcode extension...

2009-08-18 Thread Gabe Black
changeset 33837b097d69 in /z/repo/m5 details: http://repo.m5sim.org/m5?cmd=changeset;node=33837b097d69 description: X86: Decode the immediate byte opcode extension for 3dNow! instructions. diffstat: 1 file changed, 27 insertions(+), 1 deletion(-)

[m5-dev] Cron m5t...@zizzer /z/m5/regression/do-regression quick

2009-08-18 Thread Cron Daemon
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/inorder-timing passed. * build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic-ruby passed. *

Re: [m5-dev] problem with running memtest-ruby in gem5?

2009-08-18 Thread nathan binkert
I've never used the default= thing (though I do know in theory what it should do.) Does it work if you don't use the default= option? Nate On Mon, Aug 17, 2009 at 8:11 PM, soma...@cs.wisc.edu wrote: The point is that even when I compile like this: scons default=ALPHA_SE

Re: [m5-dev] problem with running memtest-ruby in gem5?

2009-08-18 Thread Steve Reinhardt
Actually the default=ALPHA_SE in Somayeh's specific command line should be a complete no-op. All default=FOO build/BAR/* does is that if there are no existing variable settings in build/variables/BAR (from a previous build) then the initial settings are read out of build_opts/FOO instead of

Re: [m5-dev] problem with running memtest-ruby in gem5?

2009-08-18 Thread Steve Reinhardt
OK, I think I see what the problem might be. In src/cpu/memtest/SConscript, we have: if 'O3CPU' in env['CPU_MODELS']: SimObject('MemTest.py') So basically the MemTest object only gets compiled in if the O3CPU is configured... that doesn't make any sense to me. I'm guessing it's just a

Re: [m5-dev] problem with running memtest-ruby in gem5?

2009-08-18 Thread Somayeh Sardashti
Thanks Steve, it solved the problem! nathan binkert wrote: OK, I think I see what the problem might be. In src/cpu/memtest/SConscript, we have: if 'O3CPU' in env['CPU_MODELS']: SimObject('MemTest.py') So basically the MemTest object only gets compiled in if the O3CPU is configured...

[m5-dev] (no subject)

2009-08-18 Thread Alexander Wood
I am out of the office until 1 October 2009. Your mail regarding will be read when I return. ___ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev