That's the architecture affected by the most recent change, but not
necessarily the architecture being used. Is the simulator itself
segfaulting, or is it a simulated segfault? The first shouldn't happen
under any normal circumstances, so if it is we need to fix that.
Gabe
Quoting ef <[email protected]>:
Parsec doesn't run in SE mode at the moment, and its probably not worth it
to make it do so.
The parsec images are compiled for ALPHA, it looks like you are running x86.
On Thu, Nov 11, 2010 at 3:14 PM, Simran Basi <[email protected]> wrote:
Has anyone managed to run the parsec benchmarks on M5 in either full-system
or syscall emulation mode?
I've also tried running the image provided by this group at UTexas
http://www.cs.utexas.edu/~parsec_m5/<http://www.cs.utexas.edu/%7Eparsec_m5/>
Has anyone managed to run the benchmarks off this image. When I try to
execute the benchmarks they all quit abruptly with a segmentation fault.
My current changeset is:
changeset: 7715:5581d0cd2bdb
tag: tip
user: Gabe Black <[email protected]>
date: Fri Oct 22 00:24:15 2010 -0700
summary: X86: Make nop a regular, non-microcoded instruction.
Please let me know if you've managed to get this to work or have some
suggestions on what to look at to fix it
Thanks,
Simran
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
