This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [wwwdocs, patch, committed] Changed some http://gcc.gnu.org to https
- From: Tobias Burnus <burnus at net-b dot de>
- To: gcc-patches <gcc-patches at gcc dot gnu dot org>, Gerald Pfeifer <gerald at pfeifer dot com>
- Date: Wed, 11 Jun 2014 20:42:57 +0200
- Subject: Re: [wwwdocs, patch, committed] Changed some http://gcc.gnu.org to https
- Authentication-results: sourceware.org; auth=none
- References: <53989616 dot 2030707 at net-b dot de>
Tobias Burnus wrote:
given that the webserver now redirects http accesses to https, it
makes sense that all references already use https.
This patch converts some more files, but I think one should at some
point change all files.
Tobias
gcc-4.7/buildstat.html | 146 ++++++++++++++++++++++++------------------------
gcc-4.7/changes.html | 62 ++++++++++----------
gcc-4.7/index.html | 10 +--
gcc-4.7/porting_to.html | 10 +--
gcc-4.8/buildstat.html | 128 +++++++++++++++++++++---------------------
gcc-4.8/changes.html | 44 +++++++-------
gcc-4.8/index.html | 10 +--
gcc-4.8/porting_to.html | 2
gcc-4.9/changes.html | 26 ++++----
gcc-4.9/porting_to.html | 8 +-
svn.html | 70 +++++++++++------------
Index: svn.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
retrieving revision 1.192
diff -u -r1.192 svn.html
--- svn.html 7 Mar 2014 20:29:16 -0000 1.192
+++ svn.html 11 Jun 2014 18:40:54 -0000
@@ -17,7 +17,7 @@
large. That way you can pick up any version (including releases) of
GCC that is in our repository.</p>
-<p>In addition you can <a href="http://gcc.gnu.org/viewcvs/";>browse
+<p>In addition you can <a href="https://gcc.gnu.org/viewcvs/gcc/";>browse
our SVN history online</a>.</p>
<p>(Our <a href="about.html#cvs">web pages are managed via CVS</a>.)</p>
@@ -41,7 +41,7 @@
the svn protocol does not work; the http protocol has a higher server
overhead associated with it and will be slower.</p>
-<p>There is more <a href="http://gcc.gnu.org/wiki/SvnHelp";>information
+<p>There is more <a href="https://gcc.gnu.org/wiki/SvnHelp";>information
about Subversion specifically for GCC</a> in the GCC Wiki.</p>
<!-- Comment out till savannah gets back to us (see above)
@@ -170,11 +170,11 @@
could use or benefit from (like data-dependence analysis,
<a href="projects/tree-ssa/lno.html">loop nest optimizations</a>).</dd>
- <dt><a href="http://gcc.gnu.org/wiki/Graphite";>graphite-branch</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/Graphite";>graphite-branch</a></dt>
<dd>The purpose of this branch is to develop an infrastructure for loop
transforms using the polyhedral model.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/LightweightIpo";>lw-ipo</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/LightweightIpo";>lw-ipo</a></dt>
<dd>This branch aims to implement lightweight IPO. Patches
and discussion on this branch should be marked with the tag
<code>[lipo]</code> in the subject line. The branch is maintained by
@@ -185,7 +185,7 @@
<dd>This branch implements a front end for GIMPLE. It is maintained
by <a href="mailto:dnovillo@google.com";>Diego Novillo</a>. Patches
should be prefixed with <code>[gimplefe]</code> in the subject line. See
- the <a href="http://gcc.gnu.org/wiki/GimpleFrontEnd";>GIMPLE Front End</a>
+ the <a href="https://gcc.gnu.org/wiki/GimpleFrontEnd";>GIMPLE Front End</a>
page for details.</dd>
<dt>gomp-4_0-branch</dt>
@@ -243,7 +243,7 @@
<dt>melt-branch</dt>
<dd>This branch is for
- a <a href="http://gcc.gnu.org/wiki/MiddleEndLispTranslator";>Middle End Lisp
+ a <a href="https://gcc.gnu.org/wiki/MiddleEndLispTranslator";>Middle End Lisp
Translator</a> branch, including both the plugin Lisp-like facility
and static analyzers developed with it. This branch is maintained
by Basile
@@ -264,13 +264,13 @@
<code>[rtl-fud]</code> in the subject line. The branch is maintained
by Steven Bosscher and Kenneth Zadeck.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/TransactionalMemory";
+ <dt><a href="https://gcc.gnu.org/wiki/TransactionalMemory";
>transactional-memory</a></dt>
<dd>This branch is for the development of transactional memory support
for GCC. Patches for this branch should be marked <code>[trans-mem]</code>
in the subject line. The branch is maintained by Richard Henderson.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/Atomic/GCCMM";>cxx-mem-model</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/Atomic/GCCMM";>cxx-mem-model</a></dt>
<dd>This branch is for the implementation of the C++ memory model.
Patches for this branch should be marked <code>[cxx-mem-model]</code>
in the subject line. The branch is maintained by Aldy Hernandez.</dd>
@@ -280,9 +280,9 @@
DWARF-4 is currently under development, so changes on this branch
will remain experimental until Version 4 is officially finalized.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/plugins";>plugins</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/plugins";>plugins</a></dt>
<dd>This branch adds plugin functionality to GCC. See the <a
- href="http://gcc.gnu.org/wiki/plugins";>plugins wiki page</a> for
+ href="https://gcc.gnu.org/wiki/plugins";>plugins wiki page</a> for
details.</dd>
<dt>no-undefined-overflow</dt>
@@ -291,12 +291,12 @@
Patches should be marked with the tag <code>[no-undefined-overflow]</code>
in the subject line. The branch is maintained by Richard Guenther.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/AndrewMacLeod/debuglocus";>debuglocus</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/AndrewMacLeod/debuglocus";>debuglocus</a></dt>
<dd>This branch is an experiment to see whether improved debug information
can be maintained throughout the compiler by associating a user decl with an
expression, statement, or insn. The name comes from attempting to utilize
the ever present source location (locus) field to carry the debug info.
- Further information can be found on the <a href="http://gcc.gnu.org/wiki/AndrewMacLeod/debuglocus";>debuglocus</a> wiki page .</dd>
+ Further information can be found on the <a href="https://gcc.gnu.org/wiki/AndrewMacLeod/debuglocus";>debuglocus</a> wiki page .</dd>
<dt>alias-export</dt>
<dd>This branch contains the alias export and data dependency export patch.
@@ -334,7 +334,7 @@
sent to this branch and discussions related to it should be marked
with the tag <code>[cxx-conversion]</code> in the subject line. For
details on working with this branch, see the
- <a href="http://gcc.gnu.org/wiki/cxx-conversion";>C++ conversion</a>
+ <a href="https://gcc.gnu.org/wiki/cxx-conversion";>C++ conversion</a>
page.</dd>
<dt>scalar-storage-order</dt>
@@ -493,7 +493,7 @@
<dt>fortran-dev</dt>
<dd>This branch is for disruptive changes to the Fortran front end,
especially for OOP development and
- the <a href="http://gcc.gnu.org/wiki/ArrayDescriptorUpdate";>
+ the <a href="https://gcc.gnu.org/wiki/ArrayDescriptorUpdate";>
array descriptor update</a>. It is maintained by Jerry DeLisle
<<a href="mailto:jvdelisle@gcc.gnu.org";>jvdelisle@gcc.gnu.org</a>>.</dd>
@@ -521,7 +521,7 @@
be marked with the tag [4_4-plugins] in the Subject line.</dd>
<dt>pph</dt>
- <dd>This branch implements <a href="http://gcc.gnu.org/wiki/pph";> Pre-Parsed
+ <dd>This branch implements <a href="https://gcc.gnu.org/wiki/pph";> Pre-Parsed
Headers for C++</a>. It is maintained by <a
href="mailto:dnovillo@google.com";>Diego Novillo</a> and <a
href="mailto:crowl@google.com";>Lawrence Crowl</a>. Patches should be
@@ -530,7 +530,7 @@
<dt>pth-icm</dt>
<dd>This is a sub-branch of the <code>pph</code> branch. It
implements
- <a href="http://gcc.gnu.org/wiki/pph#Pre-Tokenized_Headers_.28PTH.29";>
+ <a href="https://gcc.gnu.org/wiki/pph#Pre-Tokenized_Headers_.28PTH.29";>
Pre-Tokenized Headers for C++</a>. Additionally, it contains
instrumentation code in the C++ parser that was used in an
incremental compiler model (icm) to study the effects of an
@@ -720,12 +720,12 @@
gomp-20050608-branch<br />
gomp-3_0-branch<br />
fixed-point<br />
- <a href="http://gcc.gnu.org/wiki/tuples/";>gimple-tuples-branch</a><br />
+ <a href="https://gcc.gnu.org/wiki/tuples/";>gimple-tuples-branch</a><br />
c-4_5-branch<br />
alias-improvements<br />
cond-optab<br />
- <a href="http://gcc.gnu.org/wiki/Var_Tracking_Assignments";>var-tracking-assignments*-branch</a><br />
- <a href="http://gcc.gnu.org/wiki/MemRef";>mem-ref2</a><br />
+ <a href="https://gcc.gnu.org/wiki/Var_Tracking_Assignments";>var-tracking-assignments*-branch</a><br />
+ <a href="https://gcc.gnu.org/wiki/MemRef";>mem-ref2</a><br />
</dt>
<dd>These branches have been merged into the mainline.</dd>
@@ -736,7 +736,7 @@
<dt>thread-annotations</dt>
<dd>This branch contained the implementation of thread safety annotations
- and analysis (<a href="http://gcc.gnu.org/wiki/ThreadSafetyAnnotation";>http://gcc.gnu.org/wiki/ThreadSafetyAnnotation</a>).
+ and analysis (<a href="https://gcc.gnu.org/wiki/ThreadSafetyAnnotation";>https://gcc.gnu.org/wiki/ThreadSafetyAnnotation</a>).
It was superseded by the <a href="#annotalysis">annotalysis branch.</a>
</dd>
@@ -788,13 +788,13 @@
<dt>faster-compiler-branch</dt>
<dd>This was a temporary branch for compiler speedups for GCC 3.4.
- See <a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00498.html";>this
+ See <a href="https://gcc.gnu.org/ml/gcc/2002-08/msg00498.html";>this
thread</a> for discussion of possible work still to be done in this
area. The branch is unmaintained at present.</dd>
<dt>gcc-3_3-e500-branch</dt>
<dd>This branch was for backporting the PowerPC/E500 back end to GCC 3.3.
- See <a href="http://gcc.gnu.org/ml/gcc/2003-04/msg00733.html";>this
+ See <a href="https://gcc.gnu.org/ml/gcc/2003-04/msg00733.html";>this
message</a> for details.</dd>
<dt>gcc-3_4-e500-branch</dt>
@@ -951,7 +951,7 @@
<dt>mem-ssa</dt>
<dd>This branch contains the implementation of Memory SSA, a new
mechanism for representing memory operations in SSA form (<a
- href="http://gcc.gnu.org/ml/gcc/2006-02/msg00620.html";>http://gcc.gnu.org/ml/gcc/2006-02/msg00620.html</a>).
+ href="https://gcc.gnu.org/ml/gcc/2006-02/msg00620.html";>https://gcc.gnu.org/ml/gcc/2006-02/msg00620.html</a>).
The branch was maintained by Diego Novillo. It is no longer
maintained.</dd>
@@ -1004,8 +1004,8 @@
<dt>ia64-fp-model-branch</dt>
<dd>This branch was a development branch with the goal of
implementing the improvements and features discussed at the <a href=
- "http://gcc.gnu.org/wiki/ia64_floating_point";>ia64 floating point</a>
- page on the <a href="http://gcc.gnu.org/wiki/";>GCC wiki</a>. It was
+ "https://gcc.gnu.org/wiki/ia64_floating_point";>ia64 floating point</a>
+ page on the <a href="https://gcc.gnu.org/wiki/";>GCC wiki</a>. It was
maintained by Zack Weinberg <<a
href="mailto:zack@codesourcery.com";>zack@codesourcery.com</a>>.
It is no longer maintained.</dd>
@@ -1039,7 +1039,7 @@
enhancements from Apple Computer into the FSF tree; this has now been
completed. A later purpose of the branch was to implement the
Objective-C++ language in the FSF GCC source tree. The message thread
- starting <a href="http://gcc.gnu.org/ml/gcc/2003-07/msg00535.html";>here</a>
+ starting <a href="https://gcc.gnu.org/ml/gcc/2003-07/msg00535.html";>here</a>
describes this at more length. This branch was being maintained by Zem
Laski
<<a href="mailto:zlaski@apple.com";>zlaski@apple.com</a>>. It
@@ -1048,7 +1048,7 @@
<dt>libada-gnattools-branch</dt>
<dd>This is the spiritual successor to the libada branch. This branch
exists to solve
- <a href="http://gcc.gnu.org/PR5911";>bug 5911</a>
+ <a href="https://gcc.gnu.org/PR5911";>bug 5911</a>
and others, by breaking out the Ada runtime into a libada directory and
the Ada tools into a gnattools directory. Work was devoted to
cleaning up the configure and make machinery, and separating it as much
@@ -1067,7 +1067,7 @@
<dt>function-specific-branch</dt>
<dd>This branch is for development of adding function specific options to
GCC. See the GCC
- <a href="http://gcc.gnu.org/wiki/FunctionSpecificOpt";>wiki</a> for a more
+ <a href="https://gcc.gnu.org/wiki/FunctionSpecificOpt";>wiki</a> for a more
detailed project description. Patches should be marked with the tag
<code>[function-specific]</code> in the subject line.
The branch has been merged into GCC 4.4.</dd>
@@ -1085,12 +1085,12 @@
time. Patches will be marked with the tag <code>[plugin]</code>
in the subject line.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/Condate";>condate-branch</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/Condate";>condate-branch</a></dt>
<dd>The purpose of this branch is to develop a language for checking
control flow graph properties. The code of this branch has not been
merged in trunk.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/MIRO";>miro-branch</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/MIRO";>miro-branch</a></dt>
<dd>The purpose of this branch is to develop an improved Mudflap
with referent objects. The code of this branch has not been merged
in trunk.</dd>
@@ -1104,7 +1104,7 @@
<dt>mem-ref</dt>
<dd>This branch is for lowering the GIMPLE IL for memory accesses to
a flat representation. See the GCC
- <a href="http://gcc.gnu.org/wiki/MemRef";>wiki</a> for a more detailed
+ <a href="https://gcc.gnu.org/wiki/MemRef";>wiki</a> for a more detailed
project description. The branch is maintained by Richard Guenther.
Patches should be marked with the tag <code>[mem-ref]</code> in the
subject line.</dd>
@@ -1119,7 +1119,7 @@
Michael Meissner,
<a href="mailto:meissner@linux.vnet.ibm.com";>meissner@linux.vnet.ibm.com</a>.</dd>
- <dt><a href="http://gcc.gnu.org/wiki/LinkTimeOptimization";>lto</a></dt>
+ <dt><a href="https://gcc.gnu.org/wiki/LinkTimeOptimization";>lto</a></dt>
<dd>This branch implemented link-time optimization.</dd>
<dt>named-addr-spaces-branch</dt>
@@ -1138,7 +1138,7 @@
<dt>split</dt>
<dd>For development of stack splitting, as described
- on <a href="http://gcc.gnu.org/wiki/SplitStacks";>the GCC wiki</a>.
+ on <a href="https://gcc.gnu.org/wiki/SplitStacks";>the GCC wiki</a>.
This branch was maintained by Ian Lance Taylor. All changes were
merged into mainline.</dd>
@@ -1146,7 +1146,7 @@
<dd>The goal of this branch was to test Boehm's GC feasibility as the
garbage collector for GCC proper. This was a part of Google Summer
of Code project, described in detail
- at <a href="http://gcc.gnu.org/wiki/Garbage_collection_tuning";>http://gcc.gnu.org/wiki/Garbage_collection_tuning</a>. The
+ at <a href="https://gcc.gnu.org/wiki/Garbage_collection_tuning";>https://gcc.gnu.org/wiki/Garbage_collection_tuning</a>. The
branch was maintained
by <a href="mailto:laurynas.biveinis@gmail.com";>Laurynas
Biveinis</a>.</dd>
@@ -1165,7 +1165,7 @@
<dt id="annotalysis">annotalysis</dt>
<dd>This branch contains the implementation of thread safety annotations
- and analysis (<a href="http://gcc.gnu.org/wiki/ThreadSafetyAnnotation";>http://gcc.gnu.org/wiki/ThreadSafetyAnnotation</a>).
+ and analysis (<a href="https://gcc.gnu.org/wiki/ThreadSafetyAnnotation";>https://gcc.gnu.org/wiki/ThreadSafetyAnnotation</a>).
The branch was maintained by
<a href="mailto:delesley@google.com";>Delesley Hutchins</a>.</dd>
Index: gcc-4.7/buildstat.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/buildstat.html,v
retrieving revision 1.12
diff -u -r1.12 buildstat.html
--- gcc-4.7/buildstat.html 27 Apr 2014 19:55:22 -0000 1.12
+++ gcc-4.7/buildstat.html 11 Jun 2014 18:40:54 -0000
@@ -13,11 +13,11 @@
<p>Instructions for running the test suite and for submitting test results
are part of
-<a href="http://gcc.gnu.org/install/test.html";>
+<a href="https://gcc.gnu.org/install/test.html";>
Installing GCC: Testing</a>.
Instructions for reporting a successful "make bootstrap",
including a list of information to include in such a report, are part of
-<a href="http://gcc.gnu.org/install/finalinstall.html";>
+<a href="https://gcc.gnu.org/install/finalinstall.html";>
Installing GCC: Final Installation</a>.</p>
<table>
@@ -26,7 +26,7 @@
<td>alpha-dec-osf5.1b</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02967.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02967.html";>4.7.0</a>
</td>
</tr>
@@ -34,7 +34,7 @@
<td>alphaev68-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01281.html";>4.7.1</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01281.html";>4.7.1</a>
</td>
</tr>
@@ -42,12 +42,12 @@
<td>alphaev68-dec-osf5.1a</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2014-01/msg00048.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02474.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02469.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02475.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02468.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02466.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2014-01/msg00048.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02474.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02469.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02475.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02468.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02466.html";>4.7.0</a>
</td>
</tr>
@@ -55,8 +55,8 @@
<td>arm-unknown-linux-gnueabi</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01400.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01105.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01400.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01105.html";>4.7.2</a>
</td>
</tr>
@@ -64,7 +64,7 @@
<td>hppa2.0w-hp-hpux11.00</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02949.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02949.html";>4.7.2</a>,
</td>
</tr>
@@ -72,8 +72,8 @@
<td>hppa2.0w-hp-hpux11.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02311.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-04/msg00080.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02311.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-04/msg00080.html";>4.7.0</a>
</td>
</tr>
@@ -81,7 +81,7 @@
<td>hppa64-hp-hpux11.00</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-10/msg00222.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-10/msg00222.html";>4.7.2</a>
</td>
</tr>
@@ -89,8 +89,8 @@
<td>hppa64-hp-hpux11.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02408.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-04/msg00408.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02408.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-04/msg00408.html";>4.7.0</a>
</td>
</tr>
@@ -98,7 +98,7 @@
<td>i386-apple-darwin9.8.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00755.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00755.html";>4.7.2</a>
</td>
</tr>
@@ -106,8 +106,8 @@
<td>i386-apple-darwin10.8.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02291.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02742.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02291.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02742.html";>4.7.0</a>
</td>
</tr>
@@ -115,15 +115,15 @@
<td>i386-pc-solaris2.8</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00255.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00254.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-05/msg00269.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01980.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-06/msg02064.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01781.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-05/msg00527.html";>4.7.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02998.html";>4.7.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02619.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00255.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00254.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-05/msg00269.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01980.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-06/msg02064.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01781.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-05/msg00527.html";>4.7.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02998.html";>4.7.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02619.html";>4.7.0</a>
</td>
</tr>
@@ -131,9 +131,9 @@
<td>i386-pc-solaris2.9</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00227.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00226.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02618.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00227.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00226.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02618.html";>4.7.0</a>
</td>
</tr>
@@ -141,9 +141,9 @@
<td>i386-pc-solaris2.10</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-10/msg00922.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-10/msg00433.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02526.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-10/msg00922.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-10/msg00433.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02526.html";>4.7.0</a>
</td>
</tr>
@@ -151,8 +151,8 @@
<td>i386-pc-solaris2.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-05/msg02140.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02519.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-05/msg02140.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02519.html";>4.7.0</a>
</td>
</tr>
@@ -160,13 +160,13 @@
<td>i686-pc-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg02958.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg02891.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01089.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-12/msg02518.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg00199.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01316.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01315.html";>4.7.1</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg02958.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg02891.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01089.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-12/msg02518.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg00199.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01316.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01315.html";>4.7.1</a>
</td>
</tr>
@@ -174,7 +174,7 @@
<td>mips-sgi-irix6.5</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01589.html";>4.7.3</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01589.html";>4.7.3</a>
</td>
</tr>
@@ -182,7 +182,7 @@
<td>mipsel-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01258.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01258.html";>4.7.2</a>
</td>
</tr>
@@ -190,10 +190,10 @@
<td>powerpc-apple-darwin8.11.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01530.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02736.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01566.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02890.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01530.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02736.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01566.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02890.html";>4.7.0</a>
</td>
</tr>
@@ -201,7 +201,7 @@
<td>powerpc-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg00946.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-01/msg00946.html";>4.7.2</a>
</td>
</tr>
@@ -209,7 +209,7 @@
<td>s390x-ibm-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg00876.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-11/msg00876.html";>4.7.2</a>
</td>
</tr>
@@ -217,10 +217,10 @@
<td>sparc-sun-solaris2.8</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00238.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00237.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02928.html";>4.7.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02621.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00238.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00237.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02928.html";>4.7.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02621.html";>4.7.0</a>
</td>
</tr>
@@ -228,9 +228,9 @@
<td>sparc-sun-solaris2.9</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00242.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-05/msg00265.html";>4.7.3</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02620.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00242.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-05/msg00265.html";>4.7.3</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02620.html";>4.7.0</a>
</td>
</tr>
@@ -238,7 +238,7 @@
<td>sparc-sun-solaris2.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02536.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02536.html";>4.7.0</a>
</td>
</tr>
@@ -246,7 +246,7 @@
<td>sparc64-sun-solaris2.8</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-09/msg02154.html";>4.7.3</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-09/msg02154.html";>4.7.3</a>
</td>
</tr>
@@ -254,7 +254,7 @@
<td>sparc64-sun-solaris2.10</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01367.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01367.html";>4.7.2</a>
</td>
</tr>
@@ -262,7 +262,7 @@
<td>sparc-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01529.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-01/msg01529.html";>4.7.2</a>
</td>
</tr>
@@ -270,8 +270,8 @@
<td>x86_64-apple-darwin10.8.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02247.html";>4.7.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02708.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02247.html";>4.7.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02708.html";>4.7.0</a>
</td>
</tr>
@@ -279,8 +279,8 @@
<td>x86_64-apple-darwin11.3.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-05/msg02122.html";>4.7.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02630.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-05/msg02122.html";>4.7.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02630.html";>4.7.0</a>
</td>
</tr>
@@ -288,7 +288,7 @@
<td>x86_64-apple-darwin12.2.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02248.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02248.html";>4.7.2</a>
</td>
</tr>
@@ -296,7 +296,7 @@
<td>x86_64-pc-solaris2.10</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-12/msg00430.html";>4.7.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-12/msg00430.html";>4.7.2</a>
</td>
</tr>
@@ -304,9 +304,9 @@
<td>x86_64-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01675.html";>4.7.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02853.html";>4.7.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02514.html";>4.7.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-06/msg01675.html";>4.7.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02853.html";>4.7.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02514.html";>4.7.0</a>
</td>
</tr>
Index: gcc-4.7/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.137
diff -u -r1.137 changes.html
--- gcc-4.7/changes.html 11 Apr 2013 07:45:45 -0000 1.137
+++ gcc-4.7/changes.html 11 Jun 2014 18:40:55 -0000
@@ -43,7 +43,7 @@
<li>IRIX 6.5 (mips-sgi-irix6.5)</li>
<li>MIPS OpenBSD (mips*-*-openbsd*)</li>
<li>Solaris 8 (*-*-solaris2.8). Details can be found in the
- <a href="http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01263.html";>
+ <a href="https://gcc.gnu.org/ml/gcc-patches/2011-03/msg01263.html";>
announcement</a>.</li>
<li>Tru64 UNIX V5.1 (alpha*-dec-osf5.1*)</li>
</ul>
@@ -120,7 +120,7 @@
clears <code>.bss</code> and the common section
resp. initializes the <code>.data</code> and <code>.rodata</code> section
provided respective sections (or subsections thereof) are not empty,
- see <a href="http://gcc.gnu.org/PR18145";>PR18145</a>.
+ see <a href="https://gcc.gnu.org/PR18145";>PR18145</a>.
Applications that put all static storage objects into non-standard
sections and / or define all static storage objects in
assembler modules, must reference <code>__do_clear_bss</code> resp.
@@ -157,7 +157,7 @@
<li>More information on porting to GCC 4.7 from previous versions
of GCC can be found in
- the <a href="http://gcc.gnu.org/gcc-4.7/porting_to.html";>porting
+ the <a href="https://gcc.gnu.org/gcc-4.7/porting_to.html";>porting
guide</a> for this release.</li>
</ul>
@@ -333,7 +333,7 @@
<p>
For more details on transactional memory
- see <a href="http://gcc.gnu.org/wiki/TransactionalMemory";>the GCC
+ see <a href="https://gcc.gnu.org/wiki/TransactionalMemory";>the GCC
WiKi</a>.
</p>
</li>
@@ -354,7 +354,7 @@
</p>
<p>
For more details on the memory models and features, see the
- <a href="http://gcc.gnu.org/wiki/Atomic/GCCMM";>atomic wiki</a>.
+ <a href="https://gcc.gnu.org/wiki/Atomic/GCCMM";>atomic wiki</a>.
</p>
</li>
@@ -548,19 +548,19 @@
some efforts have been made to improve the support of class
scope using-declarations. In particular, using-declarations
referring to a dependent type now work as expected
- (<a href="http://gcc.gnu.org/PR14258";>bug c++/14258</a>).
+ (<a href="https://gcc.gnu.org/PR14258";>bug c++/14258</a>).
</li>
<li>The ELF symbol visibility of a template instantiation is now properly
constrained by the visibility of its template arguments
- (<a href="http://gcc.gnu.org/PR35688";>bug c++/35688</a>).</li>
+ (<a href="https://gcc.gnu.org/PR35688";>bug c++/35688</a>).</li>
</ul>
<h4>Runtime Library (libstdc++)</h4>
<ul>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/libstdc++/manual/manual/status.html#status.iso.2011";>
+ <li><a href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/libstdc++/manual/manual/status.html#status.iso.2011";>
Improved experimental support for the new ISO C++ standard, C++11</a>,
including:
<ul>
@@ -585,35 +585,35 @@
<h3 id="fortran">Fortran</h3>
<ul>
<li>The compile flag <a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfstack_002darrays_007d-254";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfstack_002darrays_007d-254";
><code>-fstack-arrays</code></a> has been added, which causes
all local arrays to be put on stack memory. For some
programs this will improve the performance significantly. If your
program uses very large local arrays, it is possible that you will
have to extend your runtime limits for stack memory.</li>
<li>The <code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Optimize-Options.html#index-Ofast-689";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Optimize-Options.html#index-Ofast-689";
>-Ofast</a></code> flag now also implies <code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfno_002dprotect_002dparens_007d-270";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfno_002dprotect_002dparens_007d-270";
>-fno-protect-parens</a></code> and <code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfstack_002darrays_007d-254";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfstack_002darrays_007d-254";
>-fstack-arrays</a></code>.</li>
<li>Front-end optimizations can now be selected by the
<code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfrontend_002doptimize_007d-275";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfrontend_002doptimize_007d-275";
>-ffrontend-optimize</a></code> option and deselected by
the <code>-fno-frontend-optimize</code> option.</li>
<li>When front-end optimization removes a function call,
<code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWfunction_002delimination_007d-170";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWfunction_002delimination_007d-170";
>-Wfunction-elimination</a></code> warns about that.</li>
<li>When performing front-end-optimization, the
<code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfaggressive_002dfunction_002delimination_007d-270";>-faggressive-function-elimination</a></code> option
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfaggressive_002dfunction_002delimination_007d-270";>-faggressive-function-elimination</a></code> option
allows the removal of duplicate function calls even for impure
functions.</li>
<li>The flag <code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWreal_002dq_002dconstant_007d-149";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWreal_002dq_002dconstant_007d-149";
>-Wreal-q-constant</a></code> has been added, which
warns if floating-point literals have been specified using
<code>q</code> (such as <code>1.0q0</code>); the <code>q</code>
@@ -621,7 +621,7 @@
(<code>REAL(16)</code> or, if not available, <code>REAL(10)</code>).
Consider using a kind parameter (such as in <code>1.0_qp</code>)
instead, which can be obtained via <a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/SELECTED_005fREAL_005fKIND.html";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/SELECTED_005fREAL_005fKIND.html";
><code>SELECTED_REAL_KIND</code></a>.</li>
<li>The <code>GFORTRAN_USE_STDERR</code> environment variable has
been removed. GNU Fortran now always prints error messages to
@@ -638,7 +638,7 @@
href="http://msdn.microsoft.com/en-us/library/bb787181%28v=vs.85%29.aspx";
>WER user-mode dumps settings</a> on Windows.</li>
<li>The <a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Debugging-Options.html#index-g_t_0040code_007bfno_002dbacktrace_007d-183";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Debugging-Options.html#index-g_t_0040code_007bfno_002dbacktrace_007d-183";
><code>-fbacktrace</code></a> option is now enabled by default.
When encountering a fatal error, gfortran will attempt to
print a backtrace to standard error before aborting. It can be
@@ -647,33 +647,33 @@
Fortran can print a backtrace with function name, file name,
line number information in addition to the addresses; otherwise
only the addresses are printed.</li>
- <li><a href="http://gcc.gnu.org/wiki/Fortran2003Status";>Fortran 2003</a>:
+ <li><a href="https://gcc.gnu.org/wiki/Fortran2003Status";>Fortran 2003</a>:
<ul>
<li>Generic interface names which have the same name as derived types
are now supported, which allows to write constructor functions. Note
that Fortran does not support static constructor functions; only
default initialization or an explicit structure-constructor
initialization are available.</li>
- <li><a href="http://gcc.gnu.org/wiki/OOP";>Polymorphic</a>
+ <li><a href="https://gcc.gnu.org/wiki/OOP";>Polymorphic</a>
(<code>class</code>) arrays are now supported.</li>
</ul></li>
- <li><a href="http://gcc.gnu.org/wiki/Fortran2008Status";>Fortran 2008</a>:
+ <li><a href="https://gcc.gnu.org/wiki/Fortran2008Status";>Fortran 2008</a>:
<ul>
<li>Support for the <code>DO CONCURRENT</code> construct has been
added, which allows the user to specify that individual loop
iterations have no interdependencies.</li>
- <li><a href="http://gcc.gnu.org/wiki/Coarray";>Coarrays</a>:
+ <li><a href="https://gcc.gnu.org/wiki/Coarray";>Coarrays</a>:
Full single-image support except for polymorphic coarrays.
Additionally, preliminary support for multiple images via an
- MPI-based <a href="http://gcc.gnu.org/wiki/CoarrayLib";>
+ MPI-based <a href="https://gcc.gnu.org/wiki/CoarrayLib";>
coarray communication library</a> has been added. Note:
The library version is not yet usable as remote coarray
access is not yet possible.</li>
</ul></li>
- <li><a href="http://gcc.gnu.org/wiki/TS29113Status";>TS 29113</a>:
+ <li><a href="https://gcc.gnu.org/wiki/TS29113Status";>TS 29113</a>:
<ul>
<li>New flag <code><a
- href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Fortran-Dialect-Options.html#index-g_t_0040code_007bstd_003d_007d_0040var_007bstd_007d-option-53";
+ href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Fortran-Dialect-Options.html#index-g_t_0040code_007bstd_003d_007d_0040var_007bstd_007d-option-53";
>-std=f2008ts</a></code> permits programs that are expected
to conform to the Fortran 2008 standard and the draft Technical
Specification (TS) 29113 on Further Interoperability of Fortran
@@ -724,7 +724,7 @@
<li>GCC now supports the XMEGA architecture.
This requires GNU binutils 2.22 or later.</li>
<li>Support for the
- <a href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Named-Address-Spaces.html";>named address spaces</a>
+ <a href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Named-Address-Spaces.html";>named address spaces</a>
<code>__flash</code>, <code>__flash1</code>, …,
<code>__flash5</code> and <code>__memx</code> has been added.
These address spaces locate read-only data in
@@ -744,9 +744,9 @@
only take effect in non-RTEMS configurations. If avr-gcc is configured
for RTEMS, the option will be ignored which is the same as
specifying <code>--with-avrlibc=no</code>.
- See <a href="http://gcc.gnu.org/PR54461";>PR54461</a> for more technical
+ See <a href="https://gcc.gnu.org/PR54461";>PR54461</a> for more technical
details.</li>
- <li>Support for AVR-specific <a href="http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/AVR-Built%5f002din-Functions.html";>built-in functions</a>
+ <li>Support for AVR-specific <a href="https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/AVR-Built%5f002din-Functions.html";>built-in functions</a>
has been added.</li>
<li>Support has been added for the signed and unsigned 24-bit scalar
integer types <code>__int24</code> and <code>__uint24</code>.</li>
@@ -1009,7 +1009,7 @@
<h2><a name="4.7.1">GCC 4.7.1</a></h2>
<p>This is the <a
-href="http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.1";>list
+href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.1";>list
of problem reports (PRs)</a> from GCC's bug tracking system that are
known to be fixed in the 4.7.1 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
@@ -1022,7 +1022,7 @@
<h2><a name="4.7.2">GCC 4.7.2</a></h2>
<p>This is the <a
-href="http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.2";>list
+href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.2";>list
of problem reports (PRs)</a> from GCC's bug tracking system that are
known to be fixed in the 4.7.2 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
@@ -1031,7 +1031,7 @@
<h2><a name="4.7.3">GCC 4.7.3</a></h2>
<p>This is the <a
-href="http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.3";>list
+href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.3";>list
of problem reports (PRs)</a> from GCC's bug tracking system that are
known to be fixed in the 4.7.3 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
Index: gcc-4.7/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/index.html,v
retrieving revision 1.7
diff -u -r1.7 index.html
--- gcc-4.7/index.html 11 Apr 2013 07:45:45 -0000 1.7
+++ gcc-4.7/index.html 11 Jun 2014 18:40:55 -0000
@@ -23,25 +23,25 @@
<dt>GCC 4.7.3</dt>
<dd><a name="4.7.3">April 11, 2013</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.7.3/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.7.3/";>documentation</a>)
</dd>
<dt>GCC 4.7.2</dt>
<dd><a name="4.7.2">September 20, 2012</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.7.2/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.7.2/";>documentation</a>)
</dd>
<dt>GCC 4.7.1</dt>
<dd><a name="4.7.1">June 14, 2012</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.7.1/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.7.1/";>documentation</a>)
</dd>
<dt>GCC 4.7.0</dt>
<dd><a name="4.7.0">March 22, 2012</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.7.0/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.7.0/";>documentation</a>)
</dd>
</dl>
@@ -58,7 +58,7 @@
<p>The GCC developers would like to thank the numerous people that have
contributed new features, improvements, bug fixes, and other changes as
well as test results to GCC.
-This <a href="http://gcc.gnu.org/onlinedocs/gcc/Contributors.html";>amazing
+This <a href="https://gcc.gnu.org/onlinedocs/gcc/Contributors.html";>amazing
group of volunteers</a> is what makes GCC successful.</p>
<p>For additional information about GCC please refer to the
Index: gcc-4.7/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/porting_to.html,v
retrieving revision 1.10
diff -u -r1.10 porting_to.html
--- gcc-4.7/porting_to.html 29 Oct 2012 20:41:57 -0000 1.10
+++ gcc-4.7/porting_to.html 11 Jun 2014 18:40:55 -0000
@@ -10,7 +10,7 @@
<p>
The GCC 4.7 release series differs from previous GCC releases in more
than the usual list of
-<a href="http://gcc.gnu.org/gcc-4.7/changes.html";>changes</a>. Some of
+<a href="https://gcc.gnu.org/gcc-4.7/changes.html";>changes</a>. Some of
these are a result of bug fixing, and some old behaviors have been
intentionally changed in order to support new standards, or relaxed
in standards-conforming ways to facilitate compilation or runtime
@@ -60,7 +60,7 @@
<p>
Many of the standard C++ library include files have been edited to no
-longer include <unistd.h> to remove <a href="http://gcc.gnu.org/PR49745";>namespace pollution</a>.
+longer include <unistd.h> to remove <a href="https://gcc.gnu.org/PR49745";>namespace pollution</a>.
</p>
<p>
@@ -106,8 +106,8 @@
<p>
The C++ compiler no longer performs some extra unqualified lookups it
had performed in the past, namely
-<a href="http://gcc.gnu.org/PR24163";>dependent base class scope lookups</a>
-and <a href="http://gcc.gnu.org/PR29131";>unqualified template function</a>
+<a href="https://gcc.gnu.org/PR24163";>dependent base class scope lookups</a>
+and <a href="https://gcc.gnu.org/PR29131";>unqualified template function</a>
lookups.
</p>
@@ -171,7 +171,7 @@
<h3>Detection of redeclared variable names in nested scopes</h3>
<p>
-The C++ compiler no longer allows identical identifiers in some <a href="http://gcc.gnu.org/PR2288";>nested scopes</a>. Namely:
+The C++ compiler no longer allows identical identifiers in some <a href="https://gcc.gnu.org/PR2288";>nested scopes</a>. Namely:
</p>
<pre>
Index: gcc-4.8/buildstat.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/buildstat.html,v
retrieving revision 1.7
diff -u -r1.7 buildstat.html
--- gcc-4.8/buildstat.html 27 Apr 2014 20:00:13 -0000 1.7
+++ gcc-4.8/buildstat.html 11 Jun 2014 18:40:55 -0000
@@ -13,11 +13,11 @@
<p>Instructions for running the test suite and for submitting test results
are part of
-<a href="http://gcc.gnu.org/install/test.html";>
+<a href="https://gcc.gnu.org/install/test.html";>
Installing GCC: Testing</a>.
Instructions for reporting a successful "make bootstrap",
including a list of information to include in such a report, are part of
-<a href="http://gcc.gnu.org/install/finalinstall.html";>
+<a href="https://gcc.gnu.org/install/finalinstall.html";>
Installing GCC: Final Installation</a>.</p>
<table>
@@ -26,7 +26,7 @@
<td>aarch64-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2014-03/msg02123.html";>4.8.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2014-03/msg02123.html";>4.8.2</a>
</td>
</tr>
@@ -34,9 +34,9 @@
<td>arm-unknown-linux-gnueabi</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01757.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg01612.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02658.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01757.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg01612.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02658.html";>4.8.0</a>
</td>
</tr>
@@ -44,7 +44,7 @@
<td>hppa-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-12/msg01923.html";>4.8.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-12/msg01923.html";>4.8.2</a>
</td>
</tr>
@@ -52,7 +52,7 @@
<td>hppa1.1-hp-hpux10.20</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-05/msg02368.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-05/msg02368.html";>4.8.0</a>
</td>
</tr>
@@ -60,7 +60,7 @@
<td>hppa2.0w-hp-hpux11.00</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg03149.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg03149.html";>4.8.0</a>
</td>
</tr>
@@ -68,8 +68,8 @@
<td>hppa2.0w-hp-hpux11.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-07/msg01045.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02538.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-07/msg01045.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02538.html";>4.8.0</a>
</td>
</tr>
@@ -77,7 +77,7 @@
<td>hppa64-hp-hpux11.00</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg00457.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg00457.html";>4.8.0</a>
</td>
</tr>
@@ -85,8 +85,8 @@
<td>hppa64-hp-hpux11.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-07/msg01207.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02679.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-07/msg01207.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02679.html";>4.8.0</a>
</td>
</tr>
@@ -94,7 +94,7 @@
<td>i386-apple-darwin10.8.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02347.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02347.html";>4.8.0</a>
</td>
</tr>
@@ -102,11 +102,11 @@
<td>i386-pc-solaris2.9</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg02068.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00230.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg00416.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg00415.html";>4.8.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02715.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg02068.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00230.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg00416.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg00415.html";>4.8.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02715.html";>4.8.0</a>
</td>
</tr>
@@ -114,7 +114,7 @@
<td>i386-pc-solaris2.10</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02626.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02626.html";>4.8.0</a>
</td>
</tr>
@@ -122,7 +122,7 @@
<td>i386-pc-solaris2.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02714.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02714.html";>4.8.0</a>
</td>
</tr>
@@ -130,10 +130,10 @@
<td>i686-pc-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01348.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01313.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-07/msg02349.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg03091.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01348.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01313.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-07/msg02349.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg03091.html";>4.8.0</a>
</td>
</tr>
@@ -141,7 +141,7 @@
<td>i686-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01351.html";>4.8.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01351.html";>4.8.2</a>
</td>
</tr>
@@ -149,8 +149,8 @@
<td>mips-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01758.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg02891.html";>4.8.1</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01758.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg02891.html";>4.8.1</a>
</td>
</tr>
@@ -158,9 +158,9 @@
<td>mipsel-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01759.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg01568.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02562.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01759.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg01568.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02562.html";>4.8.0</a>
</td>
</tr>
@@ -168,9 +168,9 @@
<td>powerpc-apple-darwin8.11.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01405.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg00237.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01012.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01405.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg00237.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg01012.html";>4.8.0</a>
</td>
</tr>
@@ -178,7 +178,7 @@
<td>powerpc-apple-darwin9.8.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg00028.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg00028.html";>4.8.0</a>
</td>
</tr>
@@ -186,7 +186,7 @@
<td>powerpc-ibm-aix6.1.0.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-04/msg00961.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-04/msg00961.html";>4.8.0</a>
</td>
</tr>
@@ -194,9 +194,9 @@
<td>powerpc-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg00014.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg01486.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02452.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-11/msg00014.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg01486.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02452.html";>4.8.0</a>
</td>
</tr>
@@ -204,7 +204,7 @@
<td>powerpc64-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-05/msg03088.html";>4.8.1</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-05/msg03088.html";>4.8.1</a>
</td>
</tr>
@@ -212,10 +212,10 @@
<td>sparc-sun-solaris2.9</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg02067.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00243.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02774.html";>4.8.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02717.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg02067.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-08/msg00243.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02774.html";>4.8.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02717.html";>4.8.0</a>
</td>
</tr>
@@ -223,7 +223,7 @@
<td>sparc-sun-solaris2.11</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02718.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02718.html";>4.8.0</a>
</td>
</tr>
@@ -231,7 +231,7 @@
<td>sparc64-sun-solaris2.9</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-09/msg02155.html";>4.8.1</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-09/msg02155.html";>4.8.1</a>
</td>
</tr>
@@ -239,9 +239,9 @@
<td>sparc64-sun-solaris2.10</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01666.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01379.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02413.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01666.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01379.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02413.html";>4.8.0</a>
</td>
</tr>
@@ -249,9 +249,9 @@
<td>sparc-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01785.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-06/msg02503.html";>4.8.1</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02660.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01785.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-06/msg02503.html";>4.8.1</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02660.html";>4.8.0</a>
</td>
</tr>
@@ -259,7 +259,7 @@
<td>x86_64-apple-darwin10.8.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02414.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02414.html";>4.8.0</a>
</td>
</tr>
@@ -267,7 +267,7 @@
<td>x86_64-apple-darwin11.4.2</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02415.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02415.html";>4.8.0</a>
</td>
</tr>
@@ -275,7 +275,7 @@
<td>x86_64-apple-darwin12.3.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02348.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02348.html";>4.8.0</a>
</td>
</tr>
@@ -283,7 +283,7 @@
<td>x86_64-apple-darwin13</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01562.html";>4.8.2</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01562.html";>4.8.2</a>
</td>
</tr>
@@ -291,7 +291,7 @@
<td>x86_64-apple-darwin13.0.0</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-07/msg00520.html";>4.8.1</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-07/msg00520.html";>4.8.1</a>
</td>
</tr>
@@ -299,12 +299,12 @@
<td>x86_64-unknown-linux-gnu</td>
<td> </td>
<td>Test results:
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2014-02/msg01608.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg00373.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01854.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01777.html";>4.8.2</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02881.html";>4.8.0</a>,
-<a href="http://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02623.html";>4.8.0</a>
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2014-02/msg01608.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-11/msg00373.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01854.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-10/msg01777.html";>4.8.2</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02881.html";>4.8.0</a>,
+<a href="https://gcc.gnu.org/ml/gcc-testresults/2013-03/msg02623.html";>4.8.0</a>
</td>
</tr>
Index: gcc-4.8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.126
diff -u -r1.126 changes.html
--- gcc-4.8/changes.html 22 May 2014 08:49:53 -0000 1.126
+++ gcc-4.8/changes.html 11 Jun 2014 18:40:55 -0000
@@ -17,7 +17,7 @@
to build GCC from sources, you will need a C++ compiler that
understands C++ 2003. For more details on the rationale and specific
changes, please refer to the <a
-href="http://gcc.gnu.org/wiki/cxx-conversion";>C++ conversion</a>
+href="https://gcc.gnu.org/wiki/cxx-conversion";>C++ conversion</a>
page.</p>
<p>To enable the Graphite framework for loop optimizations you now
@@ -54,7 +54,7 @@
GCC 4.7.2 is turned on per default for all non-RTEMS configurations.
This option arranges for a better integration of
<a href="http://www.nongnu.org/avr-libc/";>AVR Libc</a> with avr-gcc.
- For technical details, see <a href="http://gcc.gnu.org/PR54461";>PR54461</a>.
+ For technical details, see <a href="https://gcc.gnu.org/PR54461";>PR54461</a>.
To turn off the option in non-RTEMS configurations, use
<code>--with-avrlibc=no</code>. If the compiler is configured for
RTEMS, the option is always turned off.</p>
@@ -62,7 +62,7 @@
<p>
More information on porting to GCC 4.8 from previous versions
of GCC can be found in
- the <a href="http://gcc.gnu.org/gcc-4.8/porting_to.html";>porting
+ the <a href="https://gcc.gnu.org/gcc-4.8/porting_to.html";>porting
guide</a> for this release.
</p>
@@ -292,7 +292,7 @@
<h4>Runtime Library (libstdc++)</h4>
<ul>
- <li><a href="http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2011";>
+ <li><a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2011";>
Improved experimental support for the new ISO C++ standard, C++11</a>,
including:
<ul>
@@ -354,13 +354,13 @@
</ul></li>
</ul></li>
- <li>The <a href="http://gcc.gnu.org/onlinedocs/gfortran/BACKTRACE.html";>
+ <li>The <a href="https://gcc.gnu.org/onlinedocs/gfortran/BACKTRACE.html";>
<code>BACKTRACE</code></a> intrinsic subroutine has been added. It shows
a backtrace at an arbitrary place in user code; program execution
continues normally afterwards.</li>
<li>The <code><a
- href="http://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
+ href="https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
-Wc-binding-type</a></code> warning option has been added (disabled
by default). It warns if the a variable might not be C interoperable; in
particular, if the variable has been declared using an intrinsic type with
@@ -370,18 +370,18 @@
option is enabled by <code>-Wall</code>.</li>
<li>The <a
- href="http://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
+ href="https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
<code>-Wrealloc-lhs</code></a> and <code>-Wrealloc-lhs-all</code> warning
command-line options have been added, which diagnose when code to is
inserted for automatic (re)allocation of a variable during assignment.
This option can be used to decide whether it is safe to use <code><a
- href="http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html";>
+ href="https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html";>
-fno-realloc-lhs</a></code>. Additionally, it can be used to find automatic
(re)allocation in hot loops. (For arrays, replacing <q><code>var=</code></q>
by <q><code>var(:)=</code></q> disables the automatic reallocation.)</li>
<li>The <a
- href="http://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
+ href="https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
<code>-Wcompare-reals</code></a> command-line option has been added. When
this is set, warnings are issued when comparing <code>REAL</code> or
<code>COMPLEX</code> types for equality and inequality; consider replacing
@@ -390,7 +390,7 @@
<code>-Wextra</code>.</li>
<li>The <a
- href="http://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
+ href="https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html";>
<code>-Wtarget-lifetime</code></a> command-line option has been added
(enabled with <code>-Wall</code>), which warns if the pointer in a
pointer assignment might outlive its target.</li>
@@ -414,17 +414,17 @@
<code>TMPDIR</code> environment variable. If <code>TMPDIR</code> is not
defined, gfortran falls back to other methods to determine the directory
for temporary files as documented in the
- <a href="http://gcc.gnu.org/onlinedocs/gfortran/TMPDIR.html";>user
+ <a href="https://gcc.gnu.org/onlinedocs/gfortran/TMPDIR.html";>user
manual</a>.</li>
- <li><a href="http://gcc.gnu.org/wiki/Fortran2003Status";>Fortran 2003</a>:
+ <li><a href="https://gcc.gnu.org/wiki/Fortran2003Status";>Fortran 2003</a>:
<ul>
<li>Support for unlimited polymorphic variables (<code>CLASS(*)</code>)
has been added. Nonconstant character lengths are not yet
supported.</li>
</ul></li>
- <li><a href="http://gcc.gnu.org/wiki/TS29113Status";>TS 29113</a>:
+ <li><a href="https://gcc.gnu.org/wiki/TS29113Status";>TS 29113</a>:
<ul>
<li>Assumed types (<code>TYPE(*)</code>) are now supported.</li>
@@ -432,7 +432,7 @@
(<code>dimension(..)</code>) has been added. Note that currently
gfortran's own array descriptor is used, which is different from the
one defined in TS29113, see <a
- href="http://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text%2Fplain&view=co";>
+ href="https://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text%2Fplain&view=co";>
gfortran's header file</a> or use the <a
href="http://chasm-interop.sourceforge.net/";>Chasm Language
Interoperability Tools</a>.</li>
@@ -510,9 +510,9 @@
<li>
Support for the "Embedded C" fixed-point has been
added. For details, see the
- <a href="http://gcc.gnu.org/wiki/avr-gcc#Fixed-Point_Support";>
+ <a href="https://gcc.gnu.org/wiki/avr-gcc#Fixed-Point_Support";>
GCC wiki</a> and the
- <a href="http://gcc.gnu.org/onlinedocs/gcc/Fixed-Point.html";>
+ <a href="https://gcc.gnu.org/onlinedocs/gcc/Fixed-Point.html";>
user manual</a>. The support is not complete.
</li>
<li>A new print modifier <code>%r</code> for register operands in inline
@@ -584,7 +584,7 @@
<code>__builtin_cpu_is("westmere")</code> returns a positive integer if
the run-time CPU is an Intel Core i7 Westmere processor. Please refer
to the <a
- href="http://gcc.gnu.org/onlinedocs/gcc/X86-Built-in-Functions.html#X86-Built-in-Functions";>
+ href="https://gcc.gnu.org/onlinedocs/gcc/X86-Built-in-Functions.html#X86-Built-in-Functions";>
user manual</a> for the list of valid CPU names recognized.</li>
<li>A built-in function <code>__builtin_cpu_supports</code> has been
added to detect if the run-time CPU supports a particular ISA feature.
@@ -592,7 +592,7 @@
one string literal argument, the ISA feature. For example,
<code>__builtin_cpu_supports("ssse3")</code> returns a positive integer
if the run-time CPU supports SSSE3 instructions. Please refer to the <a
- href="http://gcc.gnu.org/onlinedocs/gcc/X86-Built-in-Functions.html#X86-Built-in-Functions";>
+ href="https://gcc.gnu.org/onlinedocs/gcc/X86-Built-in-Functions.html#X86-Built-in-Functions";>
user manual</a> for the list of valid ISA names recognized.</li>
</ul>
<p>Caveat: If these built-in functions are called before any static
@@ -636,7 +636,7 @@
}
</pre>
Please refer to this
- <a href="http://gcc.gnu.org/wiki/FunctionMultiVersioning";>wiki</a> for more
+ <a href="https://gcc.gnu.org/wiki/FunctionMultiVersioning";>wiki</a> for more
information.
</li>
<li> The x86 back end has been improved to allow option
@@ -882,7 +882,7 @@
<h2><a name="4.8.1">GCC 4.8.1</a></h2>
<p>This is the <a
-href="http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.1";>list
+href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.1";>list
of problem reports (PRs)</a> from GCC's bug tracking system that are
known to be fixed in the 4.8.1 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
@@ -911,7 +911,7 @@
<h2><a name="4.8.2">GCC 4.8.2</a></h2>
<p>This is the <a
-href="http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.2";>list
+href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.2";>list
of problem reports (PRs)</a> from GCC's bug tracking system that are
known to be fixed in the 4.8.2 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
@@ -920,7 +920,7 @@
<h2><a name="4.8.3">GCC 4.8.3</a></h2>
<p>This is the <a
-href="http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.3";>list
+href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.3";>list
of problem reports (PRs)</a> from GCC's bug tracking system that are
known to be fixed in the 4.8.3 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
Index: gcc-4.8/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/index.html,v
retrieving revision 1.6
diff -u -r1.6 index.html
--- gcc-4.8/index.html 22 May 2014 08:49:53 -0000 1.6
+++ gcc-4.8/index.html 11 Jun 2014 18:40:55 -0000
@@ -23,25 +23,25 @@
<dt>GCC 4.8.3</dt>
<dd><a name="4.8.3">May 22, 2014</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.8.3/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.8.3/";>documentation</a>)
</dd>
<dt>GCC 4.8.2</dt>
<dd><a name="4.8.2">October 16, 2013</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.8.2/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.8.2/";>documentation</a>)
</dd>
<dt>GCC 4.8.1</dt>
<dd><a name="4.8.1">May 31, 2013</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.8.1/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.8.1/";>documentation</a>)
</dd>
<dt>GCC 4.8.0</dt>
<dd><a name="4.8.0">March 22, 2013</a>
(<a href="changes.html">changes</a>,
- <a href="http://gcc.gnu.org/onlinedocs/4.8.0/";>documentation</a>)
+ <a href="https://gcc.gnu.org/onlinedocs/4.8.0/";>documentation</a>)
</dd>
</dl>
@@ -58,7 +58,7 @@
<p>The GCC developers would like to thank the numerous people that have
contributed new features, improvements, bug fixes, and other changes as
well as test results to GCC.
-This <a href="http://gcc.gnu.org/onlinedocs/gcc/Contributors.html";>amazing
+This <a href="https://gcc.gnu.org/onlinedocs/gcc/Contributors.html";>amazing
group of volunteers</a> is what makes GCC successful.</p>
<p>For additional information about GCC please refer to the
Index: gcc-4.8/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/porting_to.html,v
retrieving revision 1.4
diff -u -r1.4 porting_to.html
--- gcc-4.8/porting_to.html 14 Mar 2013 01:27:38 -0000 1.4
+++ gcc-4.8/porting_to.html 11 Jun 2014 18:40:55 -0000
@@ -10,7 +10,7 @@
<p>
The GCC 4.8 release series differs from previous GCC releases in more
than the usual list of
-<a href="http://gcc.gnu.org/gcc-4.8/changes.html";>changes</a>. Some of
+<a href="https://gcc.gnu.org/gcc-4.8/changes.html";>changes</a>. Some of
these are a result of bug fixing, and some old behaviors have been
intentionally changed in order to support new standards, or relaxed
in standards-conforming ways to facilitate compilation or runtime
Index: gcc-4.9/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.64
diff -u -r1.64 changes.html
--- gcc-4.9/changes.html 22 Mar 2014 14:20:02 -0000 1.64
+++ gcc-4.9/changes.html 11 Jun 2014 18:40:56 -0000
@@ -29,7 +29,7 @@
<ul>
<li>Solaris 9 (*-*-solaris2.9). Details can be found in the
- <a href="http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00728.html";>
+ <a href="https://gcc.gnu.org/ml/gcc-patches/2013-05/msg00728.html";>
announcement</a>.</li>
</ul>
</li>
@@ -38,7 +38,7 @@
<p>
More information on porting to GCC 4.9 from previous versions
of GCC can be found in
- the <a href="http://gcc.gnu.org/gcc-4.9/porting_to.html";>porting
+ the <a href="https://gcc.gnu.org/gcc-4.9/porting_to.html";>porting
guide</a> for this release.
</p>
@@ -113,7 +113,7 @@
>OpenMP specification</a> is now supported for the C and C++ compilers.
The new <code>-fopenmp-simd</code> option can be used to enable OpenMP's
SIMD directives, while ignoring other OpenMP directives. The new <a
- href="http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fsimd-cost-model-908";
+ href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-fsimd-cost-model-908";
><code>-fsimd-cost-model=</code></a> option permits to tune the
vectorization cost model for loops annotated with OpenMP and Cilk
Plus <code>simd</code> directives; <code>-Wopenmp-simd</code> warns when
@@ -136,7 +136,7 @@
<ul>
<li>Support for colorizing diagnostics emitted by GCC has been added.
The <code><a
- href="http://gcc.gnu.org/onlinedocs/gcc/Language-Independent-Options.html#index-fdiagnostics-color-246";
+ href="https://gcc.gnu.org/onlinedocs/gcc/Language-Independent-Options.html#index-fdiagnostics-color-246";
>-fdiagnostics-color=auto</a></code> will enable it when
outputting to terminals, <code>-fdiagnostics-color=always</code>
unconditionally. The <code>GCC_COLORS</code> environment variable
@@ -162,7 +162,7 @@
</pre></li>
<li>With the new <a
- href="http://gcc.gnu.org/onlinedocs/gcc/Loop-Specific-Pragmas.html";
+ href="https://gcc.gnu.org/onlinedocs/gcc/Loop-Specific-Pragmas.html";
><code>#pragma GCC ivdep</code></a>, the user can assert that there are no
loop-carried dependencies which would prevent concurrent execution of
consecutive iterations using SIMD (single instruction multiple data)
@@ -284,7 +284,7 @@
<h4>Runtime Library (libstdc++)</h4>
<ul>
- <li><a href="http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2011";>
+ <li><a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2011";>
Improved support for C++11</a>, including:
<ul>
<li> support for <code><regex></code>;</li>
@@ -294,7 +294,7 @@
meet the allocator-aware container requirements; </li>
</ul>
</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2014";>
+ <li><a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2014";>
Improved experimental support for the upcoming ISO C++ standard, C++14</a>,
including:
<ul>
@@ -343,7 +343,7 @@
<li>ABI changes:
<ul>
<li>Note that the <a
- href="http://gcc.gnu.org/onlinedocs/gfortran/Argument-passing-conventions.html";
+ href="https://gcc.gnu.org/onlinedocs/gfortran/Argument-passing-conventions.html";
>argument passing ABI</a> has changed for scalar dummy
arguments of type <code>INTEGER</code>, <code>REAL</code>,
<code>COMPLEX</code> and <code>LOGICAL</code>, which have
@@ -378,7 +378,7 @@
controlled by the <code>-Wzerotrips</code> option, which is implied by
<code>-Wall</code>.</li>
<li>The new <code>NO_ARG_CHECK</code> attribute of the <a
- href="http://gcc.gnu.org/onlinedocs/gfortran/GNU-Fortran-Compiler-Directives.html";
+ href="https://gcc.gnu.org/onlinedocs/gfortran/GNU-Fortran-Compiler-Directives.html";
><code>!GCC$</code> directive</a> can be used to disable the
type-kind-rank (TKR) argument check for a dummy argument. The feature
is similar to ISO/IEC TS 29133:2012's <code>TYPE(*)</code>, except that
@@ -397,7 +397,7 @@
rank; contrary to <code>NO_ARG_CHECK</code> assumed-rank arguments
pass an array descriptor which contains the array shape and stride
of the argument.</li>
- <li><a href="http://gcc.gnu.org/wiki/Fortran2003Status";>Fortran 2003</a>:
+ <li><a href="https://gcc.gnu.org/wiki/Fortran2003Status";>Fortran 2003</a>:
<ul>
<li>Finalization is now supported. Note that finalization is currently
only done for a subset of the situations in which it should occur.</li>
@@ -406,13 +406,13 @@
been added. (Deferred-length character variables are supported since
GCC 4.6.)</li>
</ul></li>
- <li><a href="http://gcc.gnu.org/wiki/Fortran2008Status";>Fortran 2008</a>:
+ <li><a href="https://gcc.gnu.org/wiki/Fortran2008Status";>Fortran 2008</a>:
<ul>
<li>When <code>STOP</code> or <code>ERROR STOP</code> is used to terminate
the execution and any exception (but inexact) is signaling, a warning is
printed to <code>ERROR_UNIT</code>, indicating which exceptions are
signaling. The <code><a
- href="http://gcc.gnu.org/onlinedocs/gfortran/Debugging-Options.html";
+ href="https://gcc.gnu.org/onlinedocs/gfortran/Debugging-Options.html";
>-ffpe-summary=</a></code> command-line option can be used to fine-tune
for which exception the warning should be shown.</li>
<li>Rounding on input (<code>READ</code>) is now handled on systems where
@@ -453,7 +453,7 @@
having to compile the entire file with the <code>-mxxx</code> option.
This improves the usability of x86 intrinsics and is particularly useful
when doing <a
- href="http://gcc.gnu.org/onlinedocs/gcc/Function-Multiversioning.html";
+ href="https://gcc.gnu.org/onlinedocs/gcc/Function-Multiversioning.html";
>Function Multiversioning</a>.
</li>
<li>GCC now supports the new Intel microarchitecture named Silvermont
Index: gcc-4.9/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/porting_to.html,v
retrieving revision 1.5
diff -u -r1.5 porting_to.html
--- gcc-4.9/porting_to.html 13 Mar 2014 10:19:41 -0000 1.5
+++ gcc-4.9/porting_to.html 11 Jun 2014 18:40:56 -0000
@@ -10,7 +10,7 @@
<p>
The GCC 4.9 release series differs from previous GCC releases in more
than the usual list of
-<a href="http://gcc.gnu.org/gcc-4.9/changes.html";>changes</a>. Some of
+<a href="https://gcc.gnu.org/gcc-4.9/changes.html";>changes</a>. Some of
these are a result of bug fixing, and some old behaviors have been
intentionally changed in order to support new standards, or relaxed
in standards-conforming ways to facilitate compilation or runtime
@@ -144,7 +144,7 @@
<p>
The standard says the example is ill-formed, so GCC was changed to reject it
-for <a href="http://gcc.gnu.org/PR31952";>PR31952</a>.
+for <a href="https://gcc.gnu.org/PR31952";>PR31952</a>.
To fix the error either rename one of the variables or use an additional
nested scope for the second one.
@@ -173,7 +173,7 @@
<p>
The standard says the example is ill-formed, so GCC was changed to reject it
-for <a href="http://gcc.gnu.org/PR54485";>PR54485</a>.
+for <a href="https://gcc.gnu.org/PR54485";>PR54485</a>.
To fix the error the default argument must appear when the member function
is first declared.
@@ -232,7 +232,7 @@
<p>
Matthias Klose,
- <a href="http://gcc.gnu.org/ml/gcc/2014-01/msg00237.html";>Debian test rebuild on x86_64-linux-gnu with trunk 20140118</a>
+ <a href="https://gcc.gnu.org/ml/gcc/2014-01/msg00237.html";>Debian test rebuild on x86_64-linux-gnu with trunk 20140118</a>
</p>
</body>