Hey folks.I have a design doc for a moderate in scope but significant in impact rework of how instruction execution and tracing work in gem5. This is something I've been thinking about for a while, but threw together just now to get it out there:
https://docs.google.com/document/d/1IqxBYr_arZq5G51oqmXoL5I9HiiwWMQ_t-rvHA78YPE/edit?usp=sharing This is strongly informed by an earlier design doc I wrote about how registers are handled here: https://docs.google.com/document/d/1O_u_Xq14TgreYThuZcbM3kuXFCrKvaFHA2O9poCeHSk/edit#heading=h.r067bn3rmydo It is a lot more narrowly scoped though, focusing only on operands and instruction execution at the StaticInst level, but also extends beyond what was described in that original doc. I'm biased of course, but I think there's a lot of value in reworking things as described in the doc. Please take a look at let me know what you think. Gabe
_______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
