Skip to content

Commit d14798c

Browse files
committed
fix typos
1 parent 397bb7b commit d14798c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# SELO
22

33
SELO is a bounded model checking framework for checking memory safety properties in heap-manipulating C programs.
4-
It inherits the architecture of [ESBMC](https://github.com/esbmc/esbmc) and components needed for BMC upon Separation Logic with Heap Variables(SLHV) are added into the framework.
4+
It inherits the architecture of [ESBMC](https://github.com/esbmc/esbmc) and components needed for BMC upon Separation Logic with Heap Variable(SLHV) are added into the framework.
55
SELO encodes verification conditions(VCs) in SLHV and such VC will be fed to [Z3-SLHV](https://anonymous.4open.science/r/Z3-SLHV).
66

77
## Building
@@ -85,15 +85,15 @@ cd build && cmake --build .
8585
If compiler can not find `z3++.h`, appending arg `
8686
-DCMAKE_CXX_FLAGS="-I<path_to_Z3-SLHV>/z3_slhv_lib/include"` solves the issue.
8787

88-
## Running SELO
88+
## Running
8989

9090
To run SELO, the following arguments must be included.
9191
```sh
9292
--no-library --force-malloc-success --result-only --multi-property --z3-slhv
9393
```
9494
`--z3-slhv` is a must to enable SELO using SLHV for encoding and using Z3-SLHV for backend solver.
9595

96-
We also provide a simple script `x.py`. We can easily to run SELO on a single file. For example, we run SELO on "case_1.c" in our benchmark bu the following command.
96+
We also provide a simple script `x.py`. We can easily to run SELO on a single file. For example, we run SELO on "case_1.c" in our benchmark by the following command.
9797
```sh
9898
./x.py --run ./benchmark/tests/case_1.c
9999
```

0 commit comments

Comments
 (0)