Dear M5,

I have been poking around M5 to a greater depth than before and I have a few
questions.

1.  Regarding x86, it seems that neither the in-order or out-of-order models
are yet supported.  What is the status of these efforts?  What work needs to
be done for these models (particularly o-o-o) to become usable.   I am not
particularly interested in full-system support, so the question is mostly
with respect to system-call emulation.

2.  Regarding ARM, the out-of-order model appears to be pretty far along.
 That's great!  However, there is currently no in-order model support.  Is
there work ongoing regarding this?  How far along is it?  Again, what work
needs to be done?

Lastly, when I run the se.py example config in the X86 SE configuration I
get an assertion failure. Here is the console output:

$ build/X86_SE/m5.debug configs/example/se.py
M5 Simulator System

Copyright (c) 2001-2008
The Regents of The University of Michigan
All Rights Reserved

M5 compiled Dec 20 2010 16:06:23
M5 revision 85e1847726e3 7798 default tip
M5 started Dec 21 2010 15:42:52
M5 executing on venus.cs.wisc.edu
command line: build/X86_SE/m5.debug configs/example/se.py
Global frequency set at 1000000000000 ticks per second
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
**** REAL SIMULATION ****
info: Entering event queue @ 0.  Starting simulation...
m5.debug: build/X86_SE/arch/x86/insts/macroop.hh:79: virtual StaticInstPtr
X86ISA::MacroopBase::fetchMicroop(MicroPC) const: Assertion `microPC <
numMicroops' failed.
Program aborted at cycle 500
Aborted

Is this a known problem?  Am I doing something wrong?  ARM and ALPHA both
seem to be okay.

Marc
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

Reply via email to