From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2153) id B55D83858C2C; Mon, 17 Apr 2023 12:18:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B55D83858C2C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681733926; bh=VBNHwDEdOdmejklAHIHpZtsn7u3WKYEopFGcaCFbyRw=; h=To:Subject:Date:From:From; b=niLeepL7FsaX0ROQfdIVNyyXC7cJTvbUsU8KGTFtFjL5eo6JKdjs6Dz/FlEIV17qU r/0lzQEo2U0KG3az/U5b6ak6erTVOmixNLTJrgJQuGGzC6uVY91ubaeAQBXyAX1sOQ iqJGCOVnbIUfRmUbxzaAepDI0Jtf/5k15zxMT9rY= To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. c9c688ea8bba75c48253712a8bd1fb39211bb95a X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: c06f4956bbcb13837e52f58cadf07379645b0399 X-Git-Newrev: c9c688ea8bba75c48253712a8bd1fb39211bb95a Message-Id: <20230417121846.B55D83858C2C@sourceware.org> Date: Mon, 17 Apr 2023 12:18:46 +0000 (GMT) From: Jakub Jelinek List-Id: This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via c9c688ea8bba75c48253712a8bd1fb39211bb95a (commit) from c06f4956bbcb13837e52f58cadf07379645b0399 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit c9c688ea8bba75c48253712a8bd1fb39211bb95a Author: Jakub Jelinek Date: Mon Apr 17 14:18:37 2023 +0200 Branching 13. diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html new file mode 100644 index 00000000..55d566b8 --- /dev/null +++ b/htdocs/gcc-14/changes.html @@ -0,0 +1,137 @@ + + + + + +GCC 14 Release Series — Changes, New Features, and Fixes + + + + + + +

GCC 14 Release Series
Changes, New Features, and Fixes

+ +

+This page is a "brief" summary of some of the huge number of improvements +in GCC 14. + +

+ +

Note: GCC 14 has not been released yet, so this document is +a work-in-progress.

+ + +

Caveats

+ + + +

General Improvements

+ + +

New Languages and Language specific improvements

+ + + + + + + + + + + + + + + + + + +

New Targets and Target Specific Improvements

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Operating Systems

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +

Other significant improvements

+ + + + + + + + diff --git a/htdocs/gcc-14/criteria.html b/htdocs/gcc-14/criteria.html new file mode 100644 index 00000000..dfe3ed00 --- /dev/null +++ b/htdocs/gcc-14/criteria.html @@ -0,0 +1,154 @@ + + + + + +GCC 14 Release Criteria + + + + + +

GCC 14 Release Criteria

+ +

This page provides the release criteria for GCC 14.

+ +

The GCC team (and, in particular, the Release Managers) will attempt +to meet these criteria before the release of GCC 14.

+ +

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 the 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.

+ +

Because the development of GCC is largely dependent on volunteers, +the Release Managers 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.

+ +

Languages

+ +

GCC supports several programming languages, including Ada, C, C++, +Fortran, Objective-C, Objective-C++, Go, and D. +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.

+ +

Primary and Secondary Platforms

+ +

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.

+ +

Our release criteria for primary platforms are:

+
All regressions open in Bugzilla have been analyzed, and all are +deemed 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.
+ +
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.
+
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.

+ +

Our release criteria for the secondary platforms are:

The compiler bootstraps successfully, and the C++ runtime library +builds.
The DejaGNU testsuite has been run, and a substantial majority of +the tests pass.

+ +

There are no release criteria for tertiary platforms.

+ +

In general bugs blocking the release are marked with priority P1 +(Maintaining the GCC Bugzilla database).

+ +

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 while 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.

+ +

Primary Platform List

+ +

The primary platforms are:

aarch64-none-linux-gnu
arm-linux-gnueabi
i586-unknown-freebsd
i686-pc-linux-gnu
powerpc64-unknown-linux-gnu
powerpc64le-unknown-linux-gnu
sparc-sun-solaris2.11
x86_64-pc-linux-gnu

+ +

Secondary Platform List

+ +

The secondary platforms are:

aarch64-elf
i686-apple-darwin
i686-pc-cygwin
i686-mingw32
powerpc-ibm-aix7.1.0.0
s390x-linux-gnu
mips64-linux-gnu

+ +

Code Quality and Compilation Time

+ +

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).

+ +

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 to +merit blocking the release.

+ + + ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 137 ++++++++++++++++++++++++++++++++ htdocs/{gcc-12 => gcc-14}/criteria.html | 8 +- 2 files changed, 141 insertions(+), 4 deletions(-) create mode 100644 htdocs/gcc-14/changes.html copy htdocs/{gcc-12 => gcc-14}/criteria.html (96%) hooks/post-receive -- gcc-wwwdocs

GCC 14 Release SeriesChanges, New Features, and Fixes