 gcc-5/changes.html  |   60 +++++++++++++++++++++
 gcc-5/criteria.html |  144 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 index.html          |    3 -
 3 files changed, 206 insertions(+), 1 deletion(-)

Index: htdocs/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.932
diff -u -r1.932 index.html
--- htdocs/index.html	16 Jul 2014 14:26:39 -0000	1.932
+++ htdocs/index.html	30 Jul 2014 06:30:21 -0000
@@ -161,7 +161,8 @@
 </dd>
 
 <dt><span class="version">Development:</span>
-  GCC 4.10.0 (<a href="gcc-4.9/criteria.html">release criteria</a>)
+  GCC 4.10.0 (<a href="gcc-5/criteria.html">release criteria</a>,
+  <a href="gcc-5/changes.html">changes</a>)
 </dt><dd>
   Status:
   <!--GCC 4.10 status below-->
--- /dev/null	2014-07-26 01:14:30.664046479 +0200
+++ htdocs/gcc-5/changes.html	2014-07-30 08:21:52.162229948 +0200
@@ -0,0 +1,60 @@
+<html>
+
+<head>
+<title>GCC 5 Release Series &mdash; Changes, New Features, and Fixes</title>
+</head>
+
+<!-- GCC maintainers, please do not hesitate to update/contribute entries
+     concerning those part of GCC you maintain!  2002-03-23, Gerald.
+-->
+
+<body>
+<h1>GCC 5 Release Series<br />Changes, New Features, and Fixes</h1>
+
+
+<!-- h2>Caveats</h2 -->
+
+<h2 id="general">General Optimizer Improvements</h2>
+
+<h2 id="languages">New Languages and Language specific improvements</h2>
+
+<!-- h3 id="ada">Ada</h3 -->
+<!-- h3 id="c-family">C family</h3 -->
+<!-- h3 id="c">C</h3-->
+<!-- h3 id="cxx">C++</h3-->
+  <!-- h4 id="libstdcxx">Runtime Library (libstdc++)</h4-->
+<h3 id="fortran">Fortran</h3>
+  <ul>
+    <li><a href="https://gcc.gnu.org/wiki/Fortran2003Status">Fortran 2003</a>:
+    <ul>
+      <li>The intrinsic IEEE modules (<code>IEEE_FEATURES</code>,
+	<code>IEEE_EXCEPTIONS</code> and <code>IEEE_ARITHMETIC</code>) are
+	now supported.</li>
+    </ul></li>
+    <li><a href="https://gcc.gnu.org/wiki/Fortran2008Status">Fortran 2008</a>:
+    <ul>
+      <li>Coarrays: Full experimental support of Fortran 2008's coarrays with
+	<code>-fcoarray=lib</code> except for locking and allocatable/pointer
+	components of derived-type coarrays. Note that GCC currently only ships
+	with a library which only supports a single image
+	(<code>libcaf_single</code>).</li>
+    </ul></li>
+    <li>TS18508 Additional Parallel Features in Fortran:</li>
+    <ul>
+      <li>Support for the collective intrinsic subroutines <code>CO_MAX</code>,
+	<code>CO_MIN</code> and <code>CO_SUM</code> has been added,
+	including <code>-fcoarray=lib</code> support.</li>
+      <li>Support for the new atomic intrinsics has been added, including
+	<code>-fcoarray=lib</code> support.</li>
+    </ul></li>
+  </ul>
+
+<!-- h3 id="go">Go</h3 -->
+<!--h3 id="java">Java (GCJ)</h3-->
+
+<!-- h2 id="targets">New Targets and Target Specific Improvements</h2 -->
+<!-- h2>Documentation improvements</h2-->
+<!-- h2>Other significant improvements</h2 -->
+
+</body>
+</html>
--- /dev/null	2014-07-26 01:14:30.664046479 +0200
+++ htdocs/gcc-5/criteria.html	2014-07-30 08:08:10.468688706 +0200
@@ -0,0 +1,144 @@
+<html>
+
+<head>
+<title>GCC 5 Release Criteria</title> </head>
+
+<body>
+
+<h1>GCC 5 Release Criteria</h1>
+
+<p>This page provides the release criteria for GCC 5.</p>  
+
+<p>The GCC team (and, in particular, the Release Manager) will attempt
+to meet these criteria before the release of GCC 5.</p>
+
+<p>In all cases, these criteria represent the minimum functionality
+required in order to make the release.  If this level of minimum
+functionality is not provided by a release candidate, then that
+candidate will probably not become the eventual release.  However, a
+release candidate that does meet these criteria may not necessarily
+become the official release; there may be other unforeseen issues that
+prevent release.  For example, if support for the Intel Pentium II is
+required by the release criteria, it is nevertheless unlikely that GCC
+would be released even though it did not support the Intel Pentium.</p>
+
+<p>Because the development of GCC is largely dependent on volunteers,
+the Release Manager and/or Steering Committee may eventually have to
+decide whether to make a release, even if the criteria here are not
+met.  For example, if no volunteer can be found to verify correct
+operation of a particular application program on a particular system,
+then that criterion may be abandoned.</p>
+
+<h1>Languages</h1>
+
+<p>GCC supports several programming languages, including Ada, C, C++,
+Objective-C, Fortran, and Java.  For the purposes of making releases,
+however, we will consider primarily C and C++, as those are the
+languages used by the vast majority of users.  Therefore, if, below,
+the criteria indicate, for example, that there should be no DejaGNU
+regressions on a particular platform, that criteria should be read as
+applying only to DejaGNU regressions within the C, C++, and C++
+runtime library testsuites.</p>
+
+<h1>Primary and Secondary Platforms</h1>
+
+<p>GCC targets a vast number of platforms.  We have classified these
+platforms into three categories: primary, secondary, and tertiary.
+Primary platforms are popular systems, both in the sense that there
+are many such systems in existence and in the sense that GCC is used
+frequently on those systems.  Secondary platforms are also popular
+systems, but are either somewhat less popular than the primary
+systems, or are considered duplicative from a testing perspective.
+All platforms that are neither primary nor secondary are tertiary
+platforms.</p>
+
+<p>Our release criteria for primary platforms is:</p>
+<ul>
+
+<li>
+<p>All regressions open in Bugzilla have been analyzed, and all are
+deemed as either unlikely to affect most users, or are determined to
+have a minimal impact on affected users.  For example, a
+typographical error in a diagnostic might be relatively common, but
+also has minimal impact on users.</p>
+
+<p>In general, regressions where the compiler generates incorrect
+code, or refuses to compile a valid program, will be considered to
+be sufficiently severe to block the release, unless there are
+substantial mitigating factors.</p>
+</li>  
+
+<li>The DejaGNU testsuite has been run, and compared with a run of
+the testsuite on the previous release of GCC, and no regressions are
+observed.</li>
+</ul>
+
+<p>Our release criteria for the secondary platforms is:</p>
+<ul>
+<li>The compiler bootstraps successfully, and the C++ runtime library
+builds.</li>
+
+<li>The DejaGNU testsuite has been run, and a substantial majority of
+the tests pass.</li>
+</ul>
+
+<p>There are no release criteria for tertiary platforms.</p>
+
+<p>In contrast to previous releases, we have removed all mention of
+explicit application testing.  It is our experience that, with the
+resources available, it is very difficult to methodically carry out
+such testing. However, we expect that interested users will submit
+bug reports for problems encountered building and using popular
+packages.  Therefore, we do not intend the elimination of application
+testing from our criteria to imply that we will not pay attention to
+application testing.</p>
+
+<h2>Primary Platform List</h2>
+
+<p>The primary platforms are:</p>
+<ul>
+<li>arm-linux-gnueabi</li>
+<li>i386-unknown-freebsd</li>
+<li>i686-pc-linux-gnu</li>
+<li>mipsisa64-elf</li>
+<li>powerpc64-unknown-linux-gnu</li>
+<li>sparc-sun-solaris2.10</li>
+<li>x86_64-unknown-linux-gnu</li>
+</ul>
+
+<h2>Secondary Platform List</h2>
+
+<p>The secondary platforms are:</p>
+<ul>
+<li>aarch64-elf</li>
+<li>i686-apple-darwin</li>
+<li>i686-pc-cygwin</li>
+<li>i686-mingw32</li>
+<li>powerpc-ibm-aix7.1.0.0</li>
+<li>s390x-linux-gnu</li>
+</ul>
+
+<h1>Code Quality and Compilation Time</h1>
+
+<p>In addition to correctness issues (e.g., generating incorrect code,
+or issuing an invalid diagnostic, or refusing to compile valid code),
+we will also consider code quality (i.e., the speed with which the
+generated code executes) and compilation time (i.e., the speed with
+which the compiler executes).</p>
+
+<p>It is difficult, if not impossible, to set out specific criteria
+for determining what level of regression is acceptable for these issues.
+In contrast to most correctness issues, where nothing short of correct
+is acceptable, it is reasonable to trade off behavior for code quality
+and compilation time.  For example, it may be acceptable, when
+compiling with optimization, if the compiler is slower, but generates
+superior code.  It may also be acceptable for the compiler to generate
+inferior code on some test cases if it generates substantially
+superior code on other test cases.  Therefore, the Release Manager, or
+parties to whom he or she delegates responsibility, will make
+determinations on a case-by-case basis as to whether or not a code
+quality or compilation time regression is sufficiently severe as to
+merit blocking the release.</p>
+
+</body>
+</html>
