Open Dolu1990 opened 2 years ago
Hi, I'm sorry for my late reply.
Thanks
Hi, Thanks for the replay.
Coremark/MHz in RSD is about 3.2. Recovery from branch misprediction in RSD is slow and thus it significantly reduces the total performance. I will try to improve the recovery mechanism.
Hooo, and coremark having those CRC being done with a if statement for each bit isn't realy being predictable, that's a real pain :/
RSD-env contains some proprietary material that makes it difficult to publish.
Sure, i understand, real pain on my side too that many known benchmark aren't opensource themself (ex specint) I used https://github.com/embench/embench-iot to avoid the issue a bit :)
Konata is very effective for debugging superscalar processors.
Yes, very helpfull, especialy tracking performance bug :D
. If you have any feature requests, please don't hesitate to let me know.
Thanks :)
By the way, which log file format are you using, "kanata" or "gem5-O3PipeView"?
I used the "gem5-O3PipeView" one, as i was able to produce some references with gem3-03 itself XD
I was looking for the "kanata" format, but as i wasn't finding example or a doc, i didn't tried much. But that would be something i would be interrested in, as it would provide more details.
Thanks ^^ Charles
Hi,
I was looking at some Coremark performance number to compare against https://github.com/SpinalHDL/NaxRiscv, but got multiple issues :
Would it be possible to either publish the coremark performances, or release some precompiled binaries, or open source a part of RSD-env ?
By the way, I used Konata quite a bit, it was very usefull, thanks ! :D
Charles