diff options
| author | Pieter Wuille <pieter@wuille.net> | 2021-12-15 09:19:50 -0500 |
|---|---|---|
| committer | Pieter Wuille <pieter@wuille.net> | 2021-12-15 09:19:50 -0500 |
| commit | dff0596fa0e289b2dfec3b4adbe05e0c14c11d79 (patch) | |
| tree | 1631eccfc7023142f2acbbe1162a17af26c35e7a /src/secp256k1/README.md | |
| parent | b8cc75435a0bcb6c62083ff134b1ba3d2ace50d1 (diff) | |
| parent | 86dbc4d075decb82fbba837aaa283cf0561897ad (diff) | |
| download | bitcoin-dff0596fa0e289b2dfec3b4adbe05e0c14c11d79.tar.xz | |
Update secp256k1 subtree to latest upstream master
Diffstat (limited to 'src/secp256k1/README.md')
| -rw-r--r-- | src/secp256k1/README.md | 23 |
1 files changed, 13 insertions, 10 deletions
diff --git a/src/secp256k1/README.md b/src/secp256k1/README.md index 182c29d9ce..5fc07dd4fa 100644 --- a/src/secp256k1/README.md +++ b/src/secp256k1/README.md @@ -66,18 +66,9 @@ libsecp256k1 is built using autotools: $ ./autogen.sh $ ./configure $ make - $ make check + $ make check # run the test suite $ sudo make install # optional -Exhaustive tests ------------ - - $ ./exhaustive_tests - -With valgrind, you might need to increase the max stack size: - - $ valgrind --max-stackframe=2500000 ./exhaustive_tests - Test coverage ----------- @@ -100,6 +91,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 ------------ |