create csv file from the benchmark output
This commit is contained in:
parent
26a255beb6
commit
b4b130678d
|
@ -14,6 +14,7 @@ valgrind_ctime_test
|
|||
*.exe
|
||||
*.so
|
||||
*.a
|
||||
*.csv
|
||||
!.gitignore
|
||||
|
||||
Makefile
|
||||
|
|
12
README.md
12
README.md
|
@ -100,6 +100,18 @@ To create a HTML report with coloured and annotated source code:
|
|||
$ mkdir -p coverage
|
||||
$ gcovr --exclude 'src/bench*' --html --html-details -o coverage/coverage.html
|
||||
|
||||
Benchmark
|
||||
------------
|
||||
If configured with `--enable-benchmark` (which is the default), binaries for benchmarking the libsecp256k1 functions will be present in the root directory after the build.
|
||||
|
||||
To print the benchmark result to the command line:
|
||||
|
||||
$ ./bench_name
|
||||
|
||||
To create a CSV file for the benchmark result :
|
||||
|
||||
$ ./bench_name | sed '2d;s/ \{1,\}//g' > bench_name.csv
|
||||
|
||||
Reporting a vulnerability
|
||||
------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue