Eric W Mackay via gem5-users <gem5-users <at> gem5.org> writes:
> Did you ever get this figured out? I am having the exact same problem, except > I built the ARM, O3CPU model. I see this problem even when I explicitly specify > the cpu-type as detailed. I've been trying to follow this through the Python > debugger but I can't pinpoint the problem. > > _______________________________________________ > gem5-users mailing list > gem5-users <at> gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users I answered my own question. Turns out that optparse sets all the options to their default values and then goes in and replaces any options you've specified on the command line. Since "atomic" is incompatible with the O3CPU ARM model, it wouldn't even get to parsing the arguments I specified since it checks whether the default values are legal first. This should probably be seen as a bug. _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
