diff options
| author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2014-04-25 08:30:38 +0000 |
|---|---|---|
| committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2014-04-25 08:30:38 +0000 |
| commit | c305c219ff698763271944d45a42ad8be09185f9 (patch) | |
| tree | 1f92264cccdab533de39886e7b7013971ebc38ab /doc/README.dev | |
| parent | 58bf58a9b1369cabebb991eb78d3cbc610b6aed3 (diff) | |
| download | mpfr-c305c219ff698763271944d45a42ad8be09185f9.tar.gz | |
[doc/README.dev] Completed the note about GCC's sanitizer.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@9043 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'doc/README.dev')
| -rw-r--r-- | doc/README.dev | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/README.dev b/doc/README.dev index 0ab05e556..f2335d616 100644 --- a/doc/README.dev +++ b/doc/README.dev @@ -244,7 +244,9 @@ To make a release (for the MPFR team): use a list of individual -fsanitize checks instead of "undefined". Bug report: http://llvm.org/bugs/show_bug.cgi?id=17000 - GCC 4.9 also supports "-fsanitize=undefined". + GCC 4.9 also supports "-fsanitize=undefined", but it just gives + diagnostic messages at runtime (no -fno-sanitize-recover option + like in clang). Test with both "make check" and the worst cases. |