X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=benchmarks%2Freadme.txt;h=d90fe2de87db1a457e0e7d60e5a41b28450b3953;hb=9fbc573597c8087ab0aa8e20d8835cfc2c5097a4;hp=a14780f559b519ba57b90ecc1f727218326d5f55;hpb=d2bd84a096a97ff4b8f41035c984991d0df922c1;p=riscv-tests.git

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