I ran into a similar problem a while back when building M5 on 32-bit Cygwin.
Maybe this explains the early crash here:
It looked like some updates to the flags field defined on StaticInstBase were
being truncated. I was seeing IsLastMicroop being lost, leading to
assert-fails (m5.opt) /
Hi Atieh,
You can take checkpoints within the benchmark by instrumenting the code
with the M5 magic instructions. You will need to grab a few files from
./util/m5/ and move them to the source tree of your benchmark: m5op.h,
m5ops.h and m5op_arch.S (where arch is the ISA that you're building the
Yeah, we expect Cygwin to mostly work, but I don't think anybody
actively keeps track of whether it does. It's best to use a VM or an
actual linux system for your build like you are now. If you do find a
bug, though, we'd be happy to have a fix.
Gabe
Quoting Tim Harris (RESEARCH)
Hi, Guys,
I am trying to build M5 in FS mode for alpha architecture. So I download
full system file from download page and put them in a subdirectory under and
M5 and change the system path directory in configs/common/SysPath.py
Then test my build with command,
scons build/ALPHA_FS/tests/opt
I'm using an actual Linux system (Ubuntu 10.04) on physical hardware, not
cygwin or VM.
Yu Licheng
-原始邮件-
From: Gabriel Michael Black
Sent: Thursday, June 02, 2011 1:11 AM
To: Yu Licheng
Subject: Re: [gem5-users] Aborted at X86 FS SE Mode (Solved)
Are you using Cygwin to build gem5?
Hi Joel,
Thank you so much for your help.
It would be kind of you if you would let me know, is it possible to restore
from checkpoints in SE mode?or it just works in FS mode?
Regards,
Atieh
On Wed, Jun 1, 2011 at 8:41 PM, Joel Hestness hestn...@cs.utexas.eduwrote:
Hi Atieh,
You can take
