Johnsy, MARSS isn't really suited for something like this (unless you want to add functionality to something in the writeback logic when the speculative state is committed to the architectural state).
Unless there's a need to do it from within the simulation, qemu is probably better suited for something like dumping instruction traces. See: http://thread.gmane.org/gmane.comp.emulators.qemu/16604 as a starting point. While the above link will only get you a trace of the program counter, it shouldn't be that hard to get the instruction mnemonics if you need them. Tyler > Hello all, > > Could you please provide instructions/steps to dump instruction traces > from benchmarks runs on MARSS? > If there is a previous document, please share. > > Thanks > Johnsy > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > _______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
