Hi Gabe, If we remove aliases for CPUs, then we should probably do so for the memory classes as well.
Andreas From: gem5-users <[email protected]<mailto:[email protected]>> on behalf of Gabe Black <[email protected]<mailto:[email protected]>> Reply-To: gem5 users mailing list <[email protected]<mailto:[email protected]>> Date: Tuesday, 2 May 2017 at 00:45 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [gem5-users] Removing CPU aliases in CpuConfig.py/fs.py. 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 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
