This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
WWW PATCH: Mention 4.0 release branch, etc.
- From: Mark Mitchell <mark at codesourcery dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 25 Feb 2005 00:54:18 -0800
- Subject: WWW PATCH: Mention 4.0 release branch, etc.
- Reply-to: mark at codesourcery dot com
This patch takes care of the wwwdocs updates for the 4.0 branch.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
Index: cvs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.179
diff -c -5 -p -r1.179 cvs.html
*** cvs.html 23 Feb 2005 22:56:57 -0000 1.179
--- cvs.html 25 Feb 2005 08:50:24 -0000
*************** particular releases or snapshots or the
*** 114,123 ****
--- 114,124 ----
<h3>Release and snapshot branches</h3>
<ul>
<li>gcc_ss_<i>yyyymmdd</i></li>
+ <li>gcc-4_0-branch</li>
<li>gcc_3_4_3_release</li>
<li>gcc_3_4_2_release</li>
<li>gcc_3_4_1_release</li>
<li>gcc_3_4_0_release</li>
<li>gcc-3_4-branch</li>
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.481
diff -c -5 -p -r1.481 index.html
*** index.html 7 Feb 2005 21:34:56 -0000 1.481
--- index.html 25 Feb 2005 08:50:24 -0000
*************** mission statement</a>.</p>
*** 58,73 ****
This is the last release from the 3.2.x series;
the branch has been closed after the release.
</dd>
-->
! <dt><strong>Active development (mainline):</strong>
will become GCC 4.0.0 (<a href="gcc-4.0/changes.html">current changes</a>)
</dt><dd>
! Branch status:
! <a href="http://gcc.gnu.org/ml/gcc/2005-02/msg00079.html";>2005-02-03</a>
! (<a href="develop.html#stage3">Stage 3</a>; open for bug fixes only).
</dd>
</dl>
<hr />
--- 58,77 ----
This is the last release from the 3.2.x series;
the branch has been closed after the release.
</dd>
-->
! <dt><strong>Next release series:</strong>
will become GCC 4.0.0 (<a href="gcc-4.0/changes.html">current changes</a>)
</dt><dd>
! Branch status: open for regression fixes only.
! </dd>
!
! <dt><strong>Active development (mainline):</strong>
! will become GCC 4.1.0 (<a href="gcc-4.1/changes.html">current changes</a>)
! </dt><dd>
! Branch status: frozen.
</dd>
</dl>
<hr />
Index: gcc-4.1/changes.html
===================================================================
RCS file: gcc-4.1/changes.html
diff -N gcc-4.1/changes.html
*** /dev/null 1 Jan 1970 00:00:00 -0000
--- gcc-4.1/changes.html 25 Feb 2005 08:50:27 -0000
***************
*** 0 ****
--- 1,29 ----
+ <html>
+
+ <head>
+ <title>GCC 4.1 Release Series — 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 4.1 Release Series<br />Changes, New Features, and Fixes</h1>
+
+ <h2>Caveats</h2>
+
+ <h2>General Optimizer Improvements</h2>
+
+ <h2>New Languages and Language specific improvements</h2>
+
+ <h2>New Targets and Target Specific Improvements</h2>
+
+ <h2><a name="obsolete_systems">Obsolete Systems</a></h2>
+
+ <h2>Documentation improvements</h2>
+
+ <h2>Other significant improvements</h2>
+
+ </body>
+ </html>
Index: gcc-4.1/criteria.html
===================================================================
RCS file: gcc-4.1/criteria.html
diff -N gcc-4.1/criteria.html
*** /dev/null 1 Jan 1970 00:00:00 -0000
--- gcc-4.1/criteria.html 25 Feb 2005 08:50:27 -0000
***************
*** 0 ****
--- 1,143 ----
+ <html>
+
+ <head>
+ <title>GCC 4.1 Release Criteria</title> </head>
+
+ <body>
+
+ <h1>GCC 4.1 Release Criteria</h1>
+
+ <p>This page provides the release criteria for GCC 4.1.</p>
+
+ <p>The GCC team (and, in particular, the Release Manager) will attempt
+ to meet these criteria before the release of GCC 4.1.</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 unforseen 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-none-elf</li>
+ <li>hppa2.0w-hp-hpux11.11</li>
+ <li>i686-pc-linux-gnu</li>
+ <li>i386-unknown-freebsd</li>
+ <li>mips-none-elf</li>
+ <li>powerpc-ibm-aix5.2.0.0</li>
+ <li>sparc-sun-solaris2.9</li>
+ <li>x86_64-unknown-linux-gnu</li>
+ </ul>
+
+ <h2>Secondary Platform List</h2>
+
+ <p>The secondary platforms are:</p>
+ <ul>
+ <li>powerpc-apple-darwin</li>
+ <li>powerpc-unknown-linux-gnu</li>
+ <li>i686-pc-cygwin</li>
+ <li>ia64-unknown-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>