Closed albertethon closed 4 months ago
I think @maerhart did the dhrystone build and setup here. Martin, do you have any hunch why the Dhrystone benchmark prints corrupted text on Boom? I think you had to make a few changes to Dhrystone since we don't support the full RISC-V fesvr setup that dhrystone used.
Thanks @albertethon for reporting this issue!
Yes, I made a few changes to benchmarks/common/syscalls.c
in the syscall
function to write the data printed in Dhrystone to a memory-mapped region we can access in the testbench. The testbench just starts printing char by char from the tohost_data
buffer declared in benchmarks/common/crt.S
and stops at the first \0
char or when the end of the buffer is reached. At some point, we should replace this hack with a proper implementation.
I've pushed a fix to main (551c5326f99fa0540ca51367bb61a4471785936c). Please let me know if it works for you now.
Thanks, it worked
I compiled Dhrystone benchmark using my own RISC-V toolchain. However, I faced an issue when running Boom with Dhrystone.
Output is confusing
When I used the Dhrystone version from the Git repository and executed it with Boom, I observed the following behavior:
On the other hand, after compiling Dhrystone and running it with Boom, I encountered the following behavior:
The output of boom seems wrong.
Also I encountered some warnings when compiling dhrystone:
Configure Information