diff options
| author | zimmerma <zimmerma@280ebfd0-de03-0410-8827-d642c229c3f4> | 2009-02-10 15:52:48 +0000 |
|---|---|---|
| committer | zimmerma <zimmerma@280ebfd0-de03-0410-8827-d642c229c3f4> | 2009-02-10 15:52:48 +0000 |
| commit | dde415908ca940fa3098837436140270caceae30 (patch) | |
| tree | 6bb9971034485a7f2ea63db4315cd1d8d5f52c7a /README.dev | |
| parent | 62ad943616bb10c1b279c5a82b1c9147bdafcb03 (diff) | |
| download | mpfr-dde415908ca940fa3098837436140270caceae30.tar.gz | |
[README.dev] added another example of using mpfr-gfx
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@5952 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'README.dev')
| -rw-r--r-- | README.dev | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/README.dev b/README.dev index 6c92a91de..62dab8367 100644 --- a/README.dev +++ b/README.dev @@ -80,6 +80,7 @@ To make a release (for the MPFR team): You can produce time graphs to check the thresholds are correct (and compare to the corresponding mpf functions) with mbench. For example: + $ cd mpfr/mbench $ make mpfr-gfx GMP=... MPFR=... $ ./mpfr-gfx -b16 -e320 -s16 -f2 -x3 # compares mpfr_mul and mpf_mul @@ -87,6 +88,13 @@ To make a release (for the MPFR team): # of 16 bits $ gnuplot -persist plot.gnuplot + Another example, comparing mpfr_mul and mpf_mul from 2 to 1000000 bits, + with ratio 1.1 between two sizes, 10 random values, and 10 smoothness + checks: + + $ ./mpfr-gfx -b2 -e1000000 -r1.1 -f10 -x3 -m10 + $ gnuplot -persist plot.gnuplot + Check the coverage of each source file by the test suite is at least 90% (or clearly justify any value under this threshold), and publish (for example in NEWS) the global coverage of this release. The individual |