summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat
-rw-r--r--INSTALL6
-rw-r--r--README2
-rw-r--r--TODO6
-rw-r--r--acinclude.m42
-rw-r--r--configure.ac8
-rw-r--r--doc/README.dev2
-rw-r--r--doc/mpfr.texi4
-rw-r--r--src/get_d64.c4
-rw-r--r--src/mpfr-impl.h6
-rw-r--r--src/mpfr-sassert.h2
-rw-r--r--src/mpfr.h6
-rw-r--r--src/set_d64.c4
-rw-r--r--tests/tests.c2
-rw-r--r--tests/tgeneric.c2
-rw-r--r--tests/tset_ld.c2
15 files changed, 29 insertions, 29 deletions
diff --git a/INSTALL b/INSTALL
index d8cff2d77..63a4660bc 100644
--- a/INSTALL
+++ b/INSTALL
@@ -406,8 +406,8 @@ the library of the old GMP version will be used! The best solution
is to make sure that the dynamic linker configuration is consistent
with GCC's behavior, for instance by having /usr/local/lib in
/etc/ld.so.conf or in some file from /etc/ld.so.conf.d (as Debian
-did: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395177). See
-also http://gcc.gnu.org/ml/gcc-help/2010-01/msg00171.html for more
+did: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395177). See
+also https://gcc.gnu.org/ml/gcc-help/2010-01/msg00171.html for more
information. Alternatively you can use:
* environment variables. This may sometimes be necessary. If DIR
is the installation directory of GMP, add DIR/include to your
@@ -620,7 +620,7 @@ a. Using MinGW64
The MinGW64 version of the GCC compiler is now available here:
-http://sourceforge.net/projects/mingw-w64/
+https://sourceforge.net/projects/mingw-w64/
It can build both GMP and MPFR for 64-bit Windows applications.
diff --git a/README b/README
index 7f7640abc..30695f954 100644
--- a/README
+++ b/README
@@ -81,7 +81,7 @@ can now use the "https:" scheme (a.k.a. DAV) instead of "svn:".
For more information about Subversion, please see:
* http://svnbook.red-bean.com/ (the official Subversion book);
- * http://gcc.gnu.org/wiki/SvnHelp (written for GCC developers,
+ * https://gcc.gnu.org/wiki/SvnHelp (written for GCC developers,
but interesting general information can be found there);
* http://subversion.apache.org/faq.html (the Subversion FAQ).
diff --git a/TODO b/TODO
index 69b266954..5d4319385 100644
--- a/TODO
+++ b/TODO
@@ -184,7 +184,7 @@ Table of contents:
j_n(x) = sqrt(Pi/(2x)) J_{n+1/2}(x). They should not be mixed with the
classical Bessel Functions, also noted j0, j1, jn, y0, y1, yn in C99
and mpfr.
- Cf http://en.wikipedia.org/wiki/Bessel_function#Spherical_Bessel_functions
+ Cf https://en.wikipedia.org/wiki/Bessel_function#Spherical_Bessel_functions
*Irregular Spherical Bessel Functions y_n: y_0(x) = -\cos(x)/x,
y_1(x)= -(\cos(x)/x+\sin(x))/x &
y_2(x)= (-3/x^3+1/x)\cos(x)-(3/x^2)\sin(x)
@@ -287,7 +287,7 @@ Table of contents:
(see Exercise 4.11 from Modern Computer Arithmetic, version 0.3)
The same method can be used for log, using the series for atanh, i.e.,
atanh(x) = 1/2*log((1+x)/(1-x)).
-- improve mpfr_gamma (see http://code.google.com/p/fastfunlib/). A possible
+- improve mpfr_gamma (see https://code.google.com/p/fastfunlib/). A possible
idea is to implement a fast algorithm for the argument reconstruction
gamma(x+k): instead of performing k products by x+i, we could precompute
x^2, ..., x^m for m ~ sqrt(k), and perform only sqrt(k) products.
@@ -511,4 +511,4 @@ Table of contents:
strings into newly allocated memory. I thought I'd done that in a
couple of places already. Arrays of chars are not much fun.
-- use http://gcc.gnu.org/viewcvs/trunk/config/stdint.m4 for mpfr-gmp.h
+- use https://gcc.gnu.org/viewcvs/gcc/trunk/config/stdint.m4 for mpfr-gmp.h
diff --git a/acinclude.m4 b/acinclude.m4
index 00306146b..c450ff2b2 100644
--- a/acinclude.m4
+++ b/acinclude.m4
@@ -1134,7 +1134,7 @@ dnl Needed for mpfr-longlong.h; this is currently necessary for s390.
dnl
dnl TODO: Replace this with a cleaner type size detection, as this
dnl solution only works with gcc and assumes CHAR_BIT == 8. Probably use
-dnl <stdint.h>, and <http://gcc.gnu.org/viewcvs/trunk/config/stdint.m4>
+dnl <stdint.h>, and <https://gcc.gnu.org/viewcvs/gcc/trunk/config/stdint.m4>
dnl as a fallback.
AC_DEFUN([GMP_C_ATTRIBUTE_MODE],
diff --git a/configure.ac b/configure.ac
index 1de2edacd..4844f05db 100644
--- a/configure.ac
+++ b/configure.ac
@@ -264,9 +264,9 @@ AM_PROG_AR
dnl For GCC, _Decimal64 was introduced in GCC 4.3 for some targets
dnl (note that it is not guaranteed to be available because it may
dnl be disabled in the GCC build). See:
-dnl http://gcc.gnu.org/gcc-4.3/changes.html
+dnl https://gcc.gnu.org/gcc-4.3/changes.html
dnl _Decimal64 is not yet defined in GCC for C++:
-dnl http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51364
+dnl https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51364
dnl _Decimal64 support is broken with GCC 4.6.3 and 4.7.2 on powerpc64
dnl with the mode32 ABI, e.g. "-m32 -mpowerpc64 -mtune=970 -O3"; this
dnl is detected by the x != x test below.
@@ -345,7 +345,7 @@ dnl even when the -icc option is used (contrary to what is documented
dnl on the icc man page).
dnl * When ICC is correctly detected (__ICC macro defined), unsetting
dnl the GCC variable confuses libtool. See:
-dnl http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485421
+dnl https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485421
dnl * If need be, the gcc predefined macros __GNUC_* can be disabled
dnl thanks to the -no-gcc option.
dnl * Now use -mieee-fp instead of -mp (ICC 13 says: option '-mp' is
@@ -546,7 +546,7 @@ dnl programs (such as the compiler), because the behavior could be
dnl incorrect and even have security implications.
dnl WARNING! LD_RUN_PATH is not taken into account by the GNU gold ld,
dnl e.g. from binutils-gold 2.22-5 under Debian; see
-dnl http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660813
+dnl https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660813
saved_LD_RUN_PATH="$LD_RUN_PATH"
LD_RUN_PATH="${LD_RUN_PATH:+$LD_RUN_PATH$PATH_SEPARATOR}$gmp_lib_path"
export LD_RUN_PATH
diff --git a/doc/README.dev b/doc/README.dev
index 4adb713ca..c3326c2d4 100644
--- a/doc/README.dev
+++ b/doc/README.dev
@@ -810,7 +810,7 @@ be difficult when it is in some macro expansion. For GCC users, a new
experimental -ftrack-macro-expansion option has been added in GCC 4.7.
"It allows the compiler to emit diagnostic about the current macro
expansion stack when a compilation error occurs in a macro expansion."
-<http://gcc.gnu.org/gcc-4.7/changes.html>
+<https://gcc.gnu.org/gcc-4.7/changes.html>
===========================================================================
diff --git a/doc/mpfr.texi b/doc/mpfr.texi
index 4efa8f9e2..5865752a8 100644
--- a/doc/mpfr.texi
+++ b/doc/mpfr.texi
@@ -13,7 +13,7 @@
@c Note: avoid using non-ASCII characters directly when possible,
@c as the "info" utility cannot currently handle them.
-@c http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=212549
+@c https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=212549
@copying
This manual documents how to install and use the Multiple Precision
@@ -603,7 +603,7 @@ gcc myprogram.c -lmpfr -lgmp
MPFR is built using Libtool and an application can use that to link if
desired, @MPFRpxreftop{libtool.info, GNU Libtool}
@c Note: the .info extension has been added to avoid the following bug:
-@c http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484740
+@c https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484740
@c which occurs when reading the info file from the build directory:
@c info ./mpfr or info -f ./mpfr.info
@c Due to a poor design, the "info" utility will not find the correct
diff --git a/src/get_d64.c b/src/get_d64.c
index 487de4fc6..05211f214 100644
--- a/src/get_d64.c
+++ b/src/get_d64.c
@@ -1,8 +1,8 @@
/* mpfr_get_decimal64 -- convert a multiple precision floating-point number
to a IEEE 754r decimal64 float
-See http://gcc.gnu.org/ml/gcc/2006-06/msg00691.html,
-http://gcc.gnu.org/onlinedocs/gcc/Decimal-Float.html,
+See https://gcc.gnu.org/ml/gcc/2006-06/msg00691.html,
+https://gcc.gnu.org/onlinedocs/gcc/Decimal-Float.html,
and TR 24732 <http://www.open-std.org/jtc1/sc22/wg14/www/projects#24732>.
Copyright 2006-2014 Free Software Foundation, Inc.
diff --git a/src/mpfr-impl.h b/src/mpfr-impl.h
index e68e4aef9..10005b175 100644
--- a/src/mpfr-impl.h
+++ b/src/mpfr-impl.h
@@ -116,7 +116,7 @@ http://www.gnu.org/licenses/ or write to the Free Software Foundation, Inc.,
/* Let's try to fix UINTMAX_MAX and INTMAX_MAX if these macros don't work
(e.g. with gcc -ansi -pedantic-errors in 32-bit mode under GNU/Linux),
- see <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582698>. */
+ see <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582698>. */
#ifdef _MPFR_H_HAVE_INTMAX_T
# ifdef MPFR_HAVE_INTMAX_MAX
# define MPFR_UINTMAX_MAX UINTMAX_MAX
@@ -1067,7 +1067,7 @@ typedef union { mp_size_t s; mp_limb_t l; } mpfr_size_limb_t;
/* Declare that some variable is initialized before being used (without a
dummy initialization) in order to avoid some compiler warnings. Use the
- VAR = VAR trick (see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36296#c3)
+ VAR = VAR trick (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36296#c3)
only with gcc as this is undefined behavior, and we don't know what other
compilers do (they may also be smarter). This self-initialization trick
could be disabled with future gcc versions.
@@ -1080,7 +1080,7 @@ typedef union { mp_size_t s; mp_limb_t l; } mpfr_size_limb_t;
__clang_minor__ 0
__clang_patchlevel__ 0
__clang_version__ "3.0 (tags/RELEASE_30/final)"
- (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705583 for this
+ (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705583 for this
problem with clang). */
#if defined(__GNUC__) && !defined(__clang__)
# define INITIALIZED(VAR) VAR = VAR
diff --git a/src/mpfr-sassert.h b/src/mpfr-sassert.h
index 80a2400ac..8041350e8 100644
--- a/src/mpfr-sassert.h
+++ b/src/mpfr-sassert.h
@@ -48,7 +48,7 @@ http://www.gnu.org/licenses/ or write to the Free Software Foundation, Inc.,
# if __MPFR_GNUC(4,8)
/* Get rid of annoying warnings "typedef '...' locally defined but not used"
(new in GCC 4.8). Thanks to Jonathan Wakely for this solution:
- http://gcc.gnu.org/ml/gcc-help/2013-07/msg00142.html */
+ https://gcc.gnu.org/ml/gcc-help/2013-07/msg00142.html */
# define MPFR_TYPEDEF_UNUSED __attribute__ ((unused))
# else
# define MPFR_TYPEDEF_UNUSED
diff --git a/src/mpfr.h b/src/mpfr.h
index 6083ac544..c08171377 100644
--- a/src/mpfr.h
+++ b/src/mpfr.h
@@ -410,7 +410,7 @@ __MPFR_DECLSPEC int mpfr_set_d _MPFR_PROTO ((mpfr_ptr, double, mpfr_rnd_t));
__MPFR_DECLSPEC int mpfr_set_flt _MPFR_PROTO ((mpfr_ptr, float, mpfr_rnd_t));
#ifdef MPFR_WANT_DECIMAL_FLOATS
/* _Decimal64 is not defined in C++,
- cf http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51364 */
+ cf https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51364 */
__MPFR_DECLSPEC int mpfr_set_decimal64 _MPFR_PROTO ((mpfr_ptr, _Decimal64,
mpfr_rnd_t));
#endif
@@ -892,8 +892,8 @@ __MPFR_DECLSPEC int mpfr_custom_get_kind _MPFR_PROTO ((mpfr_srcptr));
are OK since if X is a constant expression, then (unsigned long) X is
also a constant expression, so that the optimizations still work. The
warnings are probably related to the following two bugs:
- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4210
- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38470 (possibly a variant)
+ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4210
+ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38470 (possibly a variant)
and the casts could be removed once these bugs are fixed.
Casts shouldn't be used on the generic calls (to the ..._2exp functions),
where implicit conversions are performed. Indeed, having at least one
diff --git a/src/set_d64.c b/src/set_d64.c
index 5e80ca1ee..318db5382 100644
--- a/src/set_d64.c
+++ b/src/set_d64.c
@@ -1,8 +1,8 @@
/* mpfr_set_decimal64 -- convert a IEEE 754r decimal64 float to
a multiple precision floating-point number
-See http://gcc.gnu.org/ml/gcc/2006-06/msg00691.html,
-http://gcc.gnu.org/onlinedocs/gcc/Decimal-Float.html,
+See https://gcc.gnu.org/ml/gcc/2006-06/msg00691.html,
+https://gcc.gnu.org/onlinedocs/gcc/Decimal-Float.html,
and TR 24732 <http://www.open-std.org/jtc1/sc22/wg14/www/projects#24732>.
Copyright 2006-2014 Free Software Foundation, Inc.
diff --git a/tests/tests.c b/tests/tests.c
index 377c9a666..57be068d4 100644
--- a/tests/tests.c
+++ b/tests/tests.c
@@ -159,7 +159,7 @@ test_version (void)
printf (" * A bad configuration in your include/library search paths.\n"
" * An inconsistency in the include/library search paths of\n"
" your development environment; an example:\n"
- " http://gcc.gnu.org/ml/gcc-help/2010-11/msg00359.html\n"
+ " https://gcc.gnu.org/ml/gcc-help/2010-11/msg00359.html\n"
" * GMP has been upgraded after the first \"make check\".\n"
" In such a case, try again after a \"make clean\".\n"
" * A new or non-standard version naming is used in GMP.\n"
diff --git a/tests/tgeneric.c b/tests/tgeneric.c
index 9e4941b72..713e8683b 100644
--- a/tests/tgeneric.c
+++ b/tests/tgeneric.c
@@ -54,7 +54,7 @@ http://www.gnu.org/licenses/ or write to the Free Software Foundation, Inc.,
#define MAKE_STR(S) STR(S)
/* The (void *) below is needed to avoid a warning with gcc 4.2+ and functions
- * with 2 arguments. See <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36299>.
+ * with 2 arguments. See <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36299>.
*/
#define TGENERIC_FAIL(S, X, U) \
do \
diff --git a/tests/tset_ld.c b/tests/tset_ld.c
index 7617ca0fd..e7e031db3 100644
--- a/tests/tset_ld.c
+++ b/tests/tset_ld.c
@@ -37,7 +37,7 @@ check_gcc33_bug (void)
printf
("Detected optimization bug of gcc 3.3 on Alpha concerning long double\n"
"comparisons; set_ld tests might fail (set_ld won't work correctly).\n"
- "See http://gcc.gnu.org/ml/gcc-bugs/2003-10/msg00853.html for more\n"
+ "See https://gcc.gnu.org/ml/gcc-bugs/2003-10/msg00853.html for more\n"
"information.\n");
}
View Lorry Controller Status