Historically, it's been possible to refer to some of the CPU models gem5
supports by using aliases like "atomic" for the AtomicSimpleCPU, "detailed"
for the DerivO3CPU, etc. In an effort to simplify the config scripts and to
make it easier and more consistent to add new CPU models, a change is in
the works which would remove those aliases and would require you to refer
to the CPU classes using their full symobject class names. No one has yet
objected to this change, but if this would be highly disruptive for you for
some reason, please speak up now and we can talk about your situation.

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

Reply via email to