aboutsummaryrefslogtreecommitdiff
path: root/benchmarks
diff options
context:
space:
mode:
authorMehmet Oguz Derin <mehmetoguzderin@mehmetoguzderin.com>2022-06-21 11:29:29 -0700
committerGitHub <noreply@github.com>2022-06-21 11:29:29 -0700
commit8567faa64561f504c1e9a70ffec74ac1a9f2091b (patch)
tree3ff94fce3e4e2f0397362507651319170ea39229 /benchmarks
parent71ee281ad5d2a09cf47234e4463379165f218a43 (diff)
downloadriscv-tests-8567faa64561f504c1e9a70ffec74ac1a9f2091b.zip
riscv-tests-8567faa64561f504c1e9a70ffec74ac1a9f2091b.tar.gz
riscv-tests-8567faa64561f504c1e9a70ffec74ac1a9f2091b.tar.bz2
Update information about Makefile fragments (#399)
The source of benchmarks' Makefile does not use fragments anymore. This commit removes the mention of them from the readme. Signed-off-by: Mehmet Oguz Derin <mehmetoguzderin@mehmetoguzderin.com>
Diffstat (limited to 'benchmarks')
-rw-r--r--benchmarks/readme.txt6
1 files changed, 2 insertions, 4 deletions
diff --git a/benchmarks/readme.txt b/benchmarks/readme.txt
index d90fe2d..59d60b7 100644
--- a/benchmarks/readme.txt
+++ b/benchmarks/readme.txt
@@ -3,10 +3,8 @@ Benchmarks for RISCV Processor
-------------------------------------------------------------------------
The benchmarks make use of the RISCV C compiler toolchain. You will need
-to include a bmark.mk makefile fragment in each benchmark directory. The
-fragment should include the object files and a rule to actually link
-these object files into an executable. There are a couple important
-points to make about the toolchain.
+to list each benchmark in bmarks variable of Makefile. There are a couple
+important points to make about the toolchain.
+ The toolchain sets the stack pointer to memory address 0x20000 so your
main memory _must_ be larger than 0x20000 bytes or else the stack will