summaryrefslogtreecommitdiff
path: root/src/exceptions.c
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2021-04-23 21:48:23 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2021-04-23 21:48:23 +0000
commit3327a79d756fdfa7449e9d788bf37ff8e7c0a81a (patch)
treee91d71862ddc87d672a70379b45e89a5509dfbec /src/exceptions.c
parent84bfe19a4bf6bd2a20a923af50bb4f3d1c628116 (diff)
downloadmpfr-3327a79d756fdfa7449e9d788bf37ff8e7c0a81a.tar.gz
[src/exceptions.c] Added a comment about a logging issue.
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14500 280ebfd0-de03-0410-8827-d642c229c3f4
Diffstat (limited to 'src/exceptions.c')
-rw-r--r--src/exceptions.c8
1 files changed, 8 insertions, 0 deletions
diff --git a/src/exceptions.c b/src/exceptions.c
index 09d6fcf1a..e8ea1c015 100644
--- a/src/exceptions.c
+++ b/src/exceptions.c
@@ -255,6 +255,14 @@ mpfr_set_erangeflag (void)
int
mpfr_check_range (mpfr_ptr x, int t, mpfr_rnd_t rnd_mode)
{
+ /* FIXME: If the following log message is enabled, it is not always
+ output. This can be seen by adding
+ MPFR_LOG_MSG (("call mpfr_check_range\n", 0));
+ at the end of exp.c (before the return).
+ When this "call mpfr_check_range" message appears, it is not always
+ followed by the one below.
+ MPFR_LOG_MSG (("mpfr_check_range\n", 0));
+ */
if (MPFR_LIKELY (! MPFR_IS_SINGULAR (x)))
{ /* x is a non-zero FP */
mpfr_exp_t exp = MPFR_EXP (x); /* Do not use MPFR_GET_EXP */