projects
/
model-checker.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
f1be76b
)
README: more formatting, correct statement about bench.sh
author
Brian Norris
<banorris@uci.edu>
Tue, 4 Jun 2013 23:32:39 +0000
(16:32 -0700)
committer
Brian Norris
<banorris@uci.edu>
Tue, 4 Jun 2013 23:33:16 +0000
(16:33 -0700)
README.md
patch
|
blob
|
history
diff --git
a/README.md
b/README.md
index
23492eb
..
c7a4848
100644
(file)
--- a/
README.md
+++ b/
README.md
@@
-104,18
+104,18
@@
SC
Note that we also provide a series of benchmarks (distributed separately),
Note that we also provide a series of benchmarks (distributed separately),
-which can be placed under the
benchmarks/
directory. After building CDSChecker,
+which can be placed under the
`benchmarks/`
directory. After building CDSChecker,
you can build and run the benchmarks as follows:
cd benchmarks
make
./run.sh barrier/barrier -y -m 2 # runs barrier test with fairness/memory liveness
you can build and run the benchmarks as follows:
cd benchmarks
make
./run.sh barrier/barrier -y -m 2 # runs barrier test with fairness/memory liveness
- ./bench.sh # run all benchmarks
twice, with
timing results
+ ./bench.sh # run all benchmarks
and provide
timing results
Running your own code
---------------------
Running your own code
---------------------
-We provide several test and sample programs under the
test/
directory, which
+We provide several test and sample programs under the
`test/`
directory, which
should compile and run with no trouble. Of course, you likely want to test your
own code. To do so, you need to perform a few steps.
should compile and run with no trouble. Of course, you likely want to test your
own code. To do so, you need to perform a few steps.