summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-05-06 07:10:07 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2015-05-06 07:10:07 +0000
commit1fd7244fffb06f73ea177b652d4bd078c8f8c77a (patch)
tree9842c8b7967304716f135da59866c0d1b28d6cb1 /doc
parent0fabf451d65687391c0b1a99493e887668d909e8 (diff)
downloadmpfr-1fd7244fffb06f73ea177b652d4bd078c8f8c77a.tar.gz
[doc/README.dev] "To make a release": Test with GCC's AddressSanitizer
(-fsanitize=address). git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@9387 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'doc')
-rw-r--r--doc/README.dev2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/README.dev b/doc/README.dev
index bda4ee0a0..174b271d9 100644
--- a/doc/README.dev
+++ b/doc/README.dev
@@ -249,6 +249,8 @@ To make a release (for the MPFR team):
diagnostic messages at runtime, not a failure; GCC trunk supports
-fno-sanitize-recover like clang.
+ Test with GCC's AddressSanitizer (-fsanitize=address).
+
Test with both "make check" and the worst cases.
Check various warnings, in particular for obsolescent features.