===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/lists.html,v
retrieving revision 1.108
@@ -94,7 +94,7 @@
<li><b><a href="https://gcc.gnu.org/ml/jit/">jit</a></b>
is for discussion and development of
- <a href="http://gcc.gnu.org/wiki/JIT">libgccjit</a>, an experimental
+ <a href="https://gcc.gnu.org/wiki/JIT">libgccjit</a>, an experimental
library for implementing Just-In-Time compilation using GCC as a back end.
The list is intended for both users and developers of the library.
Patches for the jit branch should go to both this list and
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v
retrieving revision 1.142
@@ -84,7 +84,7 @@
<dt><span>GCC now uses C++ as its implementation language</span>
<span class="date">[2012-08-14]</span></dt>
-<dd>The <a href="http://gcc.gnu.org/wiki/cxx-conversion">cxx-conversion</a>
+<dd>The <a href="https://gcc.gnu.org/wiki/cxx-conversion">cxx-conversion</a>
branch has been merged into trunk. This switches GCC's implementation
language from C to <a href="codingconventions.html#Cxx_Conventions">C++</a>.
Additionally, some data structures have been re-implemented in C++
@@ -125,7 +125,7 @@
<dt><span>Atomic memory model support</span>
<span class="date">[2011-11-06]</span></dt>
-<dd>C++11/C11 <a href="http://gcc.gnu.org/wiki/Atomic/GCCMM">memory model</a>
+<dd>C++11/C11 <a href="https://gcc.gnu.org/wiki/Atomic/GCCMM">memory model</a>
support has been added through a new set of built-in <code>__atomic</code>
functions. Code was contributed by Andrew MacLeod, Richard Henderson, and
Aldy Hernandez, all of Red Hat, Inc.
@@ -135,14 +135,14 @@
<span class="date">[2011-11-18]</span></dt>
<dd>IUUK (Computer Science Institute, Charles University), CE-ITI
(Institute for Theoretical Computer Science) and Google are organizing
-a <a href="http://gcc.gnu.org/wiki/cauldron2012">workshop for GNU
+a <a href="https://gcc.gnu.org/wiki/cauldron2012">workshop for GNU
Tools developers</a>. The workshop will be held in July 2012 at
Charles University, Prague.</dd>
<dt><span>Transactional memory support</span>
<span class="date">[2011-11-15]</span></dt>
<dd>An implementation of the
-ongoing <a href="http://gcc.gnu.org/wiki/TransactionalMemory">transactional
+ongoing <a href="https://gcc.gnu.org/wiki/TransactionalMemory">transactional
memory</a> standard has been added. Code was contributed by Richard
Henderson, Aldy Hernandez, and Torvald Riegel, all of Red Hat, Inc.
The project was partially funded by
@@ -154,7 +154,7 @@
<dt><span>POWER7 on the GCC Compile Farm</span>
<span class="date">[2011-11-10]</span></dt>
<dd>IBM has donated a 64 processor POWER7 machine (3.55 GHz, 64 GB RAM)
-to the <a href="http://gcc.gnu.org/wiki/CompileFarm">GCC Compile Farm
+to the <a href="https://gcc.gnu.org/wiki/CompileFarm">GCC Compile Farm
project</a>. Hosting is donated by the OSU Open Source Lab.</dd>
<dt><span>Epiphany processor support</span>
@@ -283,7 +283,7 @@
<dd><a href="gcc-4.4/">GCC 4.4.2</a> has been released.</dd>
<dt>October 3, 2009</dt>
-<dd>The <a href="http://gcc.gnu.org/wiki/LinkTimeOptimization">LTO</a>
+<dd>The <a href="https://gcc.gnu.org/wiki/LinkTimeOptimization">LTO</a>
branch has been merged into trunk. The next release of GCC will
feature a new whole-program optimizer, able to perform interprocedural
optimizations across different files, even if they are written in
@@ -302,7 +302,7 @@
<dt>May 6, 2009</dt>
<dd>GCC can now be extended using a generic <a
-href="http://gcc.gnu.org/wiki/plugins-branch">plugin framework</a> on host
+href="https://gcc.gnu.org/wiki/plugins-branch">plugin framework</a> on host
platforms that support dynamically loadable objects.</dd>
<dt>April 21, 2009</dt>
@@ -345,7 +345,7 @@
<dt>May 22, 2008</dt>
<dd>AMD Developer Central has donated two bi-quad core machines with
the latest AMD Opteron 8354 "Barcelona B3" processors and 16GB of RAM
-to the <a href="http://gcc.gnu.org/wiki/CompileFarm">GCC Compile Farm
+to the <a href="https://gcc.gnu.org/wiki/CompileFarm">GCC Compile Farm
project</a> for use by free software developers. Hosting is donated
by INRIA Saclay.</dd>
@@ -443,7 +443,7 @@
GCC</a>.</dd>
<dt>January 5, 2007</dt>
-<dd><a href="http://gcc.gnu.org/wiki/mem-ssa">Memory SSA</a>, a new
+<dd><a href="https://gcc.gnu.org/wiki/mem-ssa">Memory SSA</a>, a new
representation for memory expressions in SSA form has been contributed
by Diego Novillo of Red Hat. This new mechanism improves <a
href="https://gcc.gnu.org/ml/gcc-patches/2006-12/msg00436.html">compile-times
@@ -532,7 +532,7 @@
New DECL hierarchy.
More information about these projects can be found at
-<a href="http://gcc.gnu.org/wiki/GCC_4.1_Projects">GCC 4.1 projects</a>.
+<a href="https://gcc.gnu.org/wiki/GCC_4.1_Projects">GCC 4.1 projects</a>.
</dd>
<dt><b>July 7, 2005</b></dt>
@@ -583,7 +583,7 @@
<dt><b>January 27, 2005</b></dt>
<dd>
-GCC now has a <a href="http://gcc.gnu.org/wiki/">Wiki</a>.
+GCC now has a <a href="https://gcc.gnu.org/wiki/">Wiki</a>.
</dd>
<dt><b>November 4, 2004</b></dt>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/benchmarks/index.html,v
retrieving revision 1.30
@@ -98,7 +98,7 @@
<p>
Diego Novillo compiled a collection of relevant scripts at
-<a href="http://gcc.gnu.org/wiki/PerformanceTesting">http://gcc.gnu.org/wiki/PerformanceTesting</a>
+<a href="https://gcc.gnu.org/wiki/PerformanceTesting">https://gcc.gnu.org/wiki/PerformanceTesting</a>
</p>
<h2>Openbench</h2>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/minimize.html,v
retrieving revision 1.7
@@ -33,7 +33,7 @@
construct a new testcase that reproduces the bug</a>, or <a
href="#reduce">iteratively reduce the original testcase</a>. It is
possible to <a
-href="http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction">automatically
+href="https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction">automatically
reduce testcases</a>. Most test cases can be reduced to fewer than 30
lines!</p>
@@ -63,7 +63,7 @@
the bug. For this, either use the undo function of your editor, or use
frequent backup files; alternatively, you can use <code>#if 0</code>
and <code>#endif</code>. The automatic and <em>recommended</em> way to
-<a href="http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction">reduce
+<a href="https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction">reduce
a testcase is using the Delta tool</a>.</p>
<p>If you have access to the original sources, it is better to start
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/reghunt.html,v
retrieving revision 1.17
@@ -117,7 +117,7 @@
<p> Information about checking out specific dates, <a
href="../svn.html#tags">working with branches and tags</a>, and
inspecting the commit logs is available at the <a
-href="http://gcc.gnu.org/wiki/SvnHelp">SVN Help pages in the GCC
+href="https://gcc.gnu.org/wiki/SvnHelp">SVN Help pages in the GCC
Wiki</a>.</p>
@@ -193,7 +193,7 @@
<h2 id="identify">Identify the patch</h2>
-<p>The following <a href="http://gcc.gnu.org/wiki/SvnHelp">SVN
+<p>The following <a href="https://gcc.gnu.org/wiki/SvnHelp">SVN
commands</a> are particularly useful to help you identify changes from
one version of a file to another:</p>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/fortran/index.html,v
retrieving revision 1.32
@@ -32,13 +32,13 @@
<h2>The Wiki and Getting the Compiler</h2>
<p>For additional info on GFortran developments, you may find the
-<a href="http://gcc.gnu.org/wiki/GFortran">GFortran wiki</a> useful.
+<a href="https://gcc.gnu.org/wiki/GFortran">GFortran wiki</a> useful.
Anyone may contribute information to the wiki. (Neither copyright
paperwork nor a patch review process is required.)</p>
<p>The GNU Project is about providing source code for its programs.
For convenience, a number of people regularly build binaries for different
platforms. Links to these can be found at the
-<a href="http://gcc.gnu.org/wiki/GFortran">wiki</a>. Most of the binary
+<a href="https://gcc.gnu.org/wiki/GFortran">wiki</a>. Most of the binary
executables are the latest development snapshots of GFortran and are
provided to encourage testing. We also want new users, from students
to masters of the art of Fortran, to try GFortran.
@@ -63,7 +63,7 @@
Fortran 95 compiler that complies with the ISO Fortran 95 Programming
Language standard [ISO/IEC 1539-1:1997(E)]. We are now well into
F2003 and F2008 features.
-The <a href="http://gcc.gnu.org/wiki/GFortran">GFortran
+The <a href="https://gcc.gnu.org/wiki/GFortran">GFortran
wiki</a> and <a href="http://gcc.gnu.org/bugzilla/">Bugzilla</a>
list features under development or yet to be implemented. Compiler
capability is quite extensive and includes nearly all g77 features.
@@ -74,10 +74,10 @@
<h2>Status of Compiler and Run-time Library</h2>
<p>We regularly update the
-<a href="http://gcc.gnu.org/wiki/GFortran#news">status</a>
+<a href="https://gcc.gnu.org/wiki/GFortran#news">status</a>
of the front end and run-time library development.
For a TODO list, check <a href="http://gcc.gnu.org/bugzilla/">Bugzilla</a>
-and the <a href="http://gcc.gnu.org/wiki/GFortran">GFortran wiki</a>.</p>
+and the <a href="https://gcc.gnu.org/wiki/GFortran">GFortran wiki</a>.</p>
<h2>Contributing</h2>
@@ -145,14 +145,14 @@
<p>The manuals for release and current development versions of GNU
Fortran can be downloaded from the
-<a href="http://gcc.gnu.org/wiki/GFortran#download">wiki documentation</a>
+<a href="https://gcc.gnu.org/wiki/GFortran#download">wiki documentation</a>
page or the
<a href="https://gcc.gnu.org/onlinedocs/">GCC online documents</a> page.</p>
<h2>Usage</h2>
<p>Here is a short
-<a href="http://gcc.gnu.org/wiki/GFortranUsage">explanation</a>
+<a href="https://gcc.gnu.org/wiki/GFortranUsage">explanation</a>
on how to invoke and use the compiler once you have built it (or
downloaded the binary).</p>
@@ -160,7 +160,7 @@
<p>We provide links to <a href="../readings.html#fortran">other information</a>
relevant to Fortran programmers; the
-<a href="http://gcc.gnu.org/wiki/GFortran#manuals">GFortran
+<a href="https://gcc.gnu.org/wiki/GFortran#manuals">GFortran
wiki</a> contains further links.</p>
</body>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v
retrieving revision 1.62
@@ -587,8 +587,8 @@
projects such as python were forced to use RTLD_LOCAL for (with its
resulting issues for C++ correctness). You can find more information
about using these options at <a
- href="http://gcc.gnu.org/wiki/Visibility">
- http://gcc.gnu.org/wiki/Visibility</a>.</li>
+ href="https://gcc.gnu.org/wiki/Visibility">
+ https://gcc.gnu.org/wiki/Visibility</a>.</li>
</ul>
<hr />
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.2/changes.html,v
retrieving revision 1.40
@@ -276,8 +276,8 @@
were used. However caution should be used as it can also cause
essential parts of the library to be omitted. Some of these issues are
discussed in:
- <a href="http://gcc.gnu.org/wiki/Statically_linking_libgcj">
- http://gcc.gnu.org/wiki/Statically_linking_libgcj
+ <a href="https://gcc.gnu.org/wiki/Statically_linking_libgcj">
+ https://gcc.gnu.org/wiki/Statically_linking_libgcj
</a>
</li>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.4/changes.html,v
retrieving revision 1.85
@@ -161,7 +161,7 @@
directs the compiler to not use <code>.cfi</code>
directives.</li>
- <li><p>The <a href="http://gcc.gnu.org/wiki/Graphite">Graphite</a>
+ <li><p>The <a href="https://gcc.gnu.org/wiki/Graphite">Graphite</a>
branch has been merged. This merge has brought in a new
framework for loop optimizations based on a polyhedral
intermediate representation. These optimizations apply to all
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.5/changes.html,v
retrieving revision 1.109
@@ -545,7 +545,7 @@
pointer with <code>PASS</code> attribute now have to use
<code>CLASS</code> in line with the Fortran 2003 standard; the
workaround to use <code>TYPE</code> is no longer supported.</li>
- <li><a href="http://gcc.gnu.org/wiki/OOP">Experimental, incomplete
+ <li><a href="https://gcc.gnu.org/wiki/OOP">Experimental, incomplete
support for polymorphism</a>, including <code>CLASS</code>,
<code>SELECT TYPE</code> and dynamic dispatch of type-bound
procedure calls. Some features do not work yet such as
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v
retrieving revision 1.148
@@ -521,7 +521,7 @@
<ul>
<li>Improved support for polymorphism between libraries and
programs and for complicated inheritance patterns (cf. <a
- href="http://gcc.gnu.org/wiki/OOP">object-oriented programming</a>).
+ href="https://gcc.gnu.org/wiki/OOP">object-oriented programming</a>).
</li>
<li>Experimental support of the <code>ASSOCIATE</code> construct.</li>
<li>In pointer assignments it is now possible to specify the lower
@@ -542,7 +542,7 @@
</li>
<li>Fortran 2008 support has been extended:
<ul>
- <li>Experimental <a href="http://gcc.gnu.org/wiki/Coarray">
+ <li>Experimental <a href="https://gcc.gnu.org/wiki/Coarray">
coarray support</a> (for one image only, i.e. <code>num_images() ==
1</code>); use the <a
href="https://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfcoarray_007d-233">
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/tree-ssa/index.html,v
retrieving revision 1.44
@@ -71,7 +71,7 @@
documentation (<code>doc/gccint.info</code> in GCC's build directory).</p>
<p>Many further bits of information also can be found in the <a
-href="http://gcc.gnu.org/wiki/GettingStarted">GCC Wiki</a>.</p>
+href="https://gcc.gnu.org/wiki/GettingStarted">GCC Wiki</a>.</p>
<hr />
<h3><a name="contributing">Contributing</a></h3>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/tree-ssa/vectorization.html,v
retrieving revision 1.29
@@ -117,8 +117,8 @@
This web page
is maintained by <a href="mailto:irar@il.ibm.com">Ira Rosen <irar@il.ibm.com></a>.
For a list of missing features and possible enhancements see
- <a href= "http://gcc.gnu.org/wiki/VectorizationTasks">
- http://gcc.gnu.org/wiki/VectorizationTasks</a>.
+ <a href= "https://gcc.gnu.org/wiki/VectorizationTasks">
+ https://gcc.gnu.org/wiki/VectorizationTasks</a>.
</p>
<h2><a name="using">Using the Vectorizer</a></h2>
@@ -542,8 +542,8 @@
}
</pre>
- <p> Also see <a href= "http://gcc.gnu.org/wiki/VectorizationTasks">
- http://gcc.gnu.org/wiki/VectorizationTasks</a>
+ <p> Also see <a href= "https://gcc.gnu.org/wiki/VectorizationTasks">
+ https://gcc.gnu.org/wiki/VectorizationTasks</a>
and a list of vectorizer missed-optimization PRs in GCC Bugzilla. </p>
<h2><a name="oldnews">Previous News and Status</a></h2>
@@ -574,10 +574,10 @@
<dd>The new vectorization feature that exploits intra-iteration parallelism
(to be submitted to GCC 4.3) was presented at the GCC summit last week ("Loop-aware SLP").
Also at the summit, we held a BOF on vectorization and other loop optimizations. The summary
- of the BOF can be found here: <a href="http://gcc.gnu.org/wiki/LoopOptimizationsBOF">
- http://gcc.gnu.org/wiki/LoopOptimizationsBOF</a>. Following the BOF the vectorizer's todo list
- was also updated (<a href="http://gcc.gnu.org/wiki/VectorizationTasks">
- http://gcc.gnu.org/wiki/VectorizationTasks</a>).
+ of the BOF can be found here: <a href="https://gcc.gnu.org/wiki/LoopOptimizationsBOF">
+ https://gcc.gnu.org/wiki/LoopOptimizationsBOF</a>. Following the BOF the vectorizer's todo list
+ was also updated (<a href="https://gcc.gnu.org/wiki/VectorizationTasks">
+ https://gcc.gnu.org/wiki/VectorizationTasks</a>).
</dd>
<dd>Mainline updates:
<ol>
@@ -664,8 +664,8 @@
<li>Vectorization of non consecutive (non-unit-stride) data-accesses with power-of-2 strides:
incoporated into GCC 4.3.</li>
<li>Additional vectorizer related projects planned for GCC 4.3 can be found here:
- (<a href= "http://gcc.gnu.org/wiki/AutovectBranchOptimizations">
- http://gcc.gnu.org/wiki/AutovectBranchOptimizations</a>).</li>
+ (<a href= "https://gcc.gnu.org/wiki/AutovectBranchOptimizations">
+ https://gcc.gnu.org/wiki/AutovectBranchOptimizations</a>).</li>
</ol>
</dd>
</dl>
@@ -738,8 +738,8 @@
<dt>2005-03-01</dt>
<dd>Vectorization projects for GCC 4.1: See
<a href=
- "http://gcc.gnu.org/wiki/Autovectorization_Enhancements">
- http://gcc.gnu.org/wiki/Autovectorization_Enhancements</a>. </dd>
+ "https://gcc.gnu.org/wiki/Autovectorization_Enhancements">
+ https://gcc.gnu.org/wiki/Autovectorization_Enhancements</a>. </dd>
<dd>Vectorization capabilities in GCC 4.0: See
<a href="#status4.0">2005-03-01 mainline status</a>. </dd>
</dl>
@@ -1524,8 +1524,8 @@
<li>"Loop-Aware SLP in GCC", Ira Rosen, Dorit Nuzman
and Ayal Zaks, GCC summit, July 2007.
- <a href="http://gcc.gnu.org/wiki/HomePage?action=AttachFile&do=view&target=GCC2007-Proceedings.pdf">
- http://gcc.gnu.org/wiki/HomePage?action=AttachFile&do=view&target=GCC2007-Proceedings.pdf</a></li>
+ <a href="https://gcc.gnu.org/wiki/HomePage?action=AttachFile&do=view&target=GCC2007-Proceedings.pdf">
+ https://gcc.gnu.org/wiki/HomePage?action=AttachFile&do=view&target=GCC2007-Proceedings.pdf</a></li>
<li>"Autovectorization in GCC - two years later", Dorit Nuzman and Ayal Zaks,
GCC summit, June 2006.
@@ -2400,8 +2400,8 @@
which turns out to be a front end issue.</p>
<p><b>Status:</b> In the works. See <a href=
- "http://gcc.gnu.org/wiki/Array_references_on_pointers">
- http://gcc.gnu.org/wiki/Array_references_on_pointers</a>
+ "https://gcc.gnu.org/wiki/Array_references_on_pointers">
+ https://gcc.gnu.org/wiki/Array_references_on_pointers</a>
and <a href="https://gcc.gnu.org/ml/gcc-patches/2005-05/msg01577.html">
https://gcc.gnu.org/ml/gcc-patches/2005-05/msg01577.html</a>.</p>
</li>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/testing/index.html,v
retrieving revision 1.33
@@ -119,7 +119,7 @@
do local builds, run the testsuite, visualize test result differences
and probably use something like
<a href="http://buildbot.net/">BuildBot</a>. Some of the
- <a href="http://gcc.gnu.org/wiki/CompileFarm">Compile Farm</a> machines
+ <a href="https://gcc.gnu.org/wiki/CompileFarm">Compile Farm</a> machines
could also be used.</li>
</ul>