[doc/README.dev] Updated some URL's (http → https).

(merged changeset r13376 from the trunk)

git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/branches/4.0@13377 280ebfd0-de03-0410-8827-d642c229c3f4

1 files changed, 10 insertions, 10 deletions

diff --git a/doc/README.dev b/doc/README.dev
index 0ad37b994..1b014afff 100644
--- a/doc/README.dev
+++ b/doc/README.dev
@@ -194,7 +194,7 @@ To make a release (for the MPFR team):
      may miss some incompatibilities.
      Update the FAQ.html file with update-faq (and check it) in the doc
      directory.
-     [*] http://lvc.github.io/abi-compliance-checker/
+     [*] https://lvc.github.io/abi-compliance-checker/
 
   4) Update the ChangeLog file with "TZ=UTC svn log -rHEAD:0 -v" in
      UTF-8 locales, e.g. "LC_ALL=en_US.UTF8 TZ=UTC svn log -rHEAD:0 -v".
@@ -250,7 +250,7 @@ To make a release (for the MPFR team):
      Also test --enable-gmp-internals with it.
 
      Try different compilers, e.g., icc, opencc (x86_64 machines),
-     tcc <http://bellard.org/tcc/>, llvm-gcc, clang.
+     tcc <https://bellard.org/tcc/>, llvm-gcc, clang.
 
      On 64-bit PowerPC, test against GMP built with the different ABI's:
      32, mode32 and mode64 (in particular mode32, where long's have
@@ -312,7 +312,7 @@ To make a release (for the MPFR team):
      but this needs:
        * GCC 4.9+
        * a patched autoconf:
-     http://lists.gnu.org/archive/html/autoconf-patches/2014-01/msg00003.html
+     https://lists.gnu.org/archive/html/autoconf-patches/2014-01/msg00003.html
 
      Check that there are no abnormal regressions in the timings (both
      for 100, 1000, 10000 digits, http://mpfr.org/mpfr-current/timings.html,
@@ -619,7 +619,7 @@ flash memory. Don't use "new", which is reserved in C++.
 
 Check C++ reserved keywords, e.g. from
 
-  http://en.cppreference.com/w/cpp/keyword
+  https://en.cppreference.com/w/cpp/keyword
 
 or more generally:
 
@@ -637,8 +637,8 @@ When a string literal ("...") is followed by a macro name, there
 must be white space between them, otherwise this is parsed as a
 user-defined string literal in C++11:
 
-  http://en.cppreference.com/w/cpp/language/user_literal
-  http://stackoverflow.com/a/6402166/3782797
+  https://en.cppreference.com/w/cpp/language/user_literal
+  https://stackoverflow.com/a/6402166/3782797
 
    =====================================================================
 
@@ -665,7 +665,7 @@ or by adding a configure test to reject the compiler.
 
 Some references:
 * https://en.wikipedia.org/wiki/Type_punning#Use_of_union
-* http://stackoverflow.com/questions/346622/opinions-on-type-punning-in-c
+* https://stackoverflow.com/questions/346622/opinions-on-type-punning-in-c
   "Opinions on type-punning in C++?"
 
 ===========================================================================
@@ -712,7 +712,7 @@ such as OSF/1 (Tru64) 5.1. This is consistent with autoconf, which
 has used this form since 2004-01-26 (in headers.m4).
 
 References:
-  http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=62ac9bbfebe879581dabeed78c6ac66b907dd51d
+  https://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=62ac9bbfebe879581dabeed78c6ac66b907dd51d
   https://sympa.inria.fr/sympa/arc/mpfr/2010-08/msg00015.html
 
 ===========================================================================
@@ -1023,7 +1023,7 @@ expansion stack when a compilation error occurs in a macro expansion."
 ===========================================================================
 
 Bit Twiddling Hacks - Sean Eron Anderson maintain a list of tricks to get
-efficient code on <http://graphics.stanford.edu/~seander/bithacks.html>.
+efficient code on <https://graphics.stanford.edu/~seander/bithacks.html>.
 WARNING: some of those tricks may not take into account possible overflows,
 and may not be portable.
 
@@ -1199,7 +1199,7 @@ Use assertions (MPFR_ASSERTN) instead.
 When using GNU extensions (based on the value of the __GNUC_* macros), check
 whether they work with ICC. The following paper can give useful information:
 "Intel® Compilers for Linux*: Compatibility with GNU Compilers" at
-<http://software.intel.com/articles/intel-compilers-for-linux-compatibility-with-gnu-compilers>.
+<https://software.intel.com/articles/intel-compilers-for-linux-compatibility-with-gnu-compilers>.
 
 To detect compilers, see