Mohammad Khasawneh
2017-12-15 15:57:02 UTC
Hello,
Iâm trying to get SPEC2017 to run in SE mode (X86) as SPEC2006 did, so far the only benchmark that ran to completion is 505.mcf_r with no modifications to the basic config file. Here is what I did:
1. Compiled benchmarks statically (although it seems this is no longer a requirement on newer gem5 versions).
2. Made sure binaries execute natively on host.
3. Ran them through gem5 pretty much like I used to run SPEC2006.
What I get:
On many of them a common error I get is this:
panic: Unrecognized/invalid instruction executed:
{
leg = 0x10,
rex = 0,
vex/xop = 0x5,
op = {
type = three byte 0f3a,
op = 0x18,
},
modRM = 0,
sib = 0,
immediate = 0,
displacement = 0
dispSize = 0
}
Iâm assuming a change in the config file would force the compiler to produce more sensible binaries, any ideas on where I should start digging would be appreciated.
Thank you,
Mohammad
Iâm trying to get SPEC2017 to run in SE mode (X86) as SPEC2006 did, so far the only benchmark that ran to completion is 505.mcf_r with no modifications to the basic config file. Here is what I did:
1. Compiled benchmarks statically (although it seems this is no longer a requirement on newer gem5 versions).
2. Made sure binaries execute natively on host.
3. Ran them through gem5 pretty much like I used to run SPEC2006.
What I get:
On many of them a common error I get is this:
panic: Unrecognized/invalid instruction executed:
{
leg = 0x10,
rex = 0,
vex/xop = 0x5,
op = {
type = three byte 0f3a,
op = 0x18,
},
modRM = 0,
sib = 0,
immediate = 0,
displacement = 0
dispSize = 0
}
Iâm assuming a change in the config file would force the compiler to produce more sensible binaries, any ideas on where I should start digging would be appreciated.
Thank you,
Mohammad