diff options
| author | Andrew Waterman <andrew@sifive.com> | 2017-03-21 17:04:49 -0700 |
|---|---|---|
| committer | Andrew Waterman <andrew@sifive.com> | 2017-03-21 17:04:49 -0700 |
| commit | 9fbc573597c8087ab0aa8e20d8835cfc2c5097a4 (patch) | |
| tree | 469c6767566934c0e723dd269e611447bdea65a8 /benchmarks/readme.txt | |
| parent | d2bd84a096a97ff4b8f41035c984991d0df922c1 (diff) | |
| download | riscv-tests-9fbc573597c8087ab0aa8e20d8835cfc2c5097a4.zip riscv-tests-9fbc573597c8087ab0aa8e20d8835cfc2c5097a4.tar.gz riscv-tests-9fbc573597c8087ab0aa8e20d8835cfc2c5097a4.tar.bz2 | |
Remove smips/host-debugging cruft
Diffstat (limited to 'benchmarks/readme.txt')
| -rw-r--r-- | benchmarks/readme.txt | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/benchmarks/readme.txt b/benchmarks/readme.txt index a14780f..d90fe2d 100644 --- a/benchmarks/readme.txt +++ b/benchmarks/readme.txt @@ -37,13 +37,6 @@ points to make about the toolchain. about how to write assembly in C here: http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html - + If you look at the example benchmarks you will see that I have two - important macros HOST_DEBUG and VERIFY. Use HOST_DEBUG to compile the - benchmark on your host workstation (ie use standard gcc on Athena/Linux - box) and then debug the benchmark. Since you are using standard gcc you - can use printf's to make sure that your benchmark actually works before - trying it out on your RISCV processor. - + Debugging C compiled code on the RISCV processor is a real pain. It is hard to associate the assembly with the C code and there is no debugger. So if you encounter a bug in your processor when running a C |