summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorvlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2021-07-15 13:40:27 +0000
committervlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4>2021-07-15 13:40:27 +0000
commit71343caf9061c77471325210d47b304dac9031ec (patch)
tree9ab0086db0ac22ae54f1ceff4d0996d1df8adb93
parent81fefed30e5c394ffedf0d71e78c5806cdea41b7 (diff)
downloadmpfr-71343caf9061c77471325210d47b304dac9031ec.tar.gz
[src/ieee_floats.h] URL update (http → https).
git-svn-id: https://scm.gforge.inria.fr/anonscm/svn/mpfr/trunk@14549 280ebfd0-de03-0410-8827-d642c229c3f4
-rw-r--r--src/ieee_floats.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/ieee_floats.h b/src/ieee_floats.h
index 9006ac511..42d7a804f 100644
--- a/src/ieee_floats.h
+++ b/src/ieee_floats.h
@@ -47,7 +47,7 @@ union dbl_bytes {
quiet NaN (qNaN) or a signaling NaN (sNaN). For instance, HP PA-RISC
is known to do the opposite way of the usual choice recommended in
IEEE 754-2008; see:
- http://grouper.ieee.org/groups/1788/email/msg03272.html
+ https://grouper.ieee.org/groups/1788/email/msg03272.html
Moreover, the right choice is to generate a qNaN in particular because
signaling NaNs are not supported by all compilers (note that the support