public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 480d1c0c0c779a9729fedbb9187fd43969a1984f Date: Thu, 30 Apr 2020 15:50:58 +0000 (GMT) [thread overview] Message-ID: <20200430155058.7DCAB3898524@sourceware.org> (raw) 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 480d1c0c0c779a9729fedbb9187fd43969a1984f (commit) from e9db7dd717c5ddcb6c3fb35d1d57f2737fa8c5df (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 480d1c0c0c779a9729fedbb9187fd43969a1984f Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Apr 30 17:49:40 2020 +0200 Branching GCC 11. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html new file mode 100644 index 00000000..707bcce7 --- /dev/null +++ b/htdocs/gcc-11/changes.html @@ -0,0 +1,139 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<title>GCC 11 Release Series — Changes, New Features, and Fixes</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" /> +</head> + +<!-- GCC maintainers, please do not hesitate to contribute/update + entries concerning those part of GCC you maintain! +--> + +<body> +<h1>GCC 11 Release Series<br/>Changes, New Features, and Fixes</h1> + +<p> +This page is a "brief" summary of some of the huge number of improvements +in GCC 11. +<!-- +You may also want to check out our +<a href="porting_to.html">Porting to GCC 11</a> page and the +<a href="../onlinedocs/index.html#current">full GCC documentation</a>. +--> +</p> + +<p>Note: GCC 11 has not been released yet, so this document is +a work-in-progress.</p> + +<!-- .................................................................. --> +<h2>Caveats</h2> +<ul> + <li>...</li> +</ul> + + +<!-- .................................................................. --> +<h2 id="general">General Improvements</h2> + +<!-- .................................................................. --> +<h2 id="languages">New Languages and Language specific improvements</h2> + +<!-- <h3 id="ada">Ada</h3> --> + +<!-- <h3 id="brig">BRIG (HSAIL)</h3> --> + +<!-- <h3 id="c-family">C family</h3> --> + +<!-- <h3 id="cxx">C++</h3> --> +<!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> --> + +<!-- <h3 id="fortran">Fortran</h3> --> + +<!-- <h3 id="go">Go</h3> --> + +<!-- .................................................................. --> +<!-- <h2 id="jit">libgccjit</h2> --> + +<!-- .................................................................. --> +<h2 id="targets">New Targets and Target Specific Improvements</h2> + +<!-- <h3 id="aarch64">AArch64</h3> --> + +<!-- <h3 id="arc">ARC</h3> --> + +<!-- <h3 id="arm">ARM</h3> --> + +<!-- <h3 id="avr">AVR</h3> --> + +<!-- <h3 id="hsa">Heterogeneous Systems Architecture</h3> --> + +<!-- <h3 id="x86">IA-32/x86-64</h3> --> + +<!-- <h3 id="mips">MIPS</h3> --> + +<!-- <h3 id="mep">MeP</h3> --> + +<!-- <h3 id="msp430">MSP430</h3> --> + +<!-- <h3 id="nds32">NDS32</h3> --> + +<!-- <h3 id="nios2">Nios II</h3> --> + +<!-- <h3 id="nvptx">NVPTX</h3> --> + +<!-- <h3 id="hppa">PA-RISC</h3> --> + +<!-- <h3 id="powerpc">PowerPC / PowerPC64 / RS6000</h3> --> + +<!-- <h3 id="s390">S/390, System z, IBM z Systems</h3> --> + +<!-- <h3 id="riscv">RISC-V</h3> --> + +<!-- <h3 id="rx">RX</h3> --> + +<!-- <h3 id="sh">SH</h3> --> + +<!-- <h3 id="sparc">SPARC</h3> --> + +<!-- <h3 id="Tile">Tile</h3> --> + +<!-- .................................................................. --> +<h2 id="os">Operating Systems</h2> + +<!-- <h3 id="aix">AIX</h3> --> + +<!-- <h3 id="fuchsia">Fuchsia</h3> --> + +<!-- <h3 id="dragonfly">DragonFly BSD</h3> --> + +<!-- <h3 id="freebsd">FreeBSD</h3> --> + +<!-- <h3 id="gnulinux">GNU/Linux</h3> --> + +<!-- <h3 id="rtems">RTEMS</h3> --> + +<!-- <h3 id="solaris">Solaris</h3> --> + +<!-- <h3 id="vxmils">VxWorks MILS</h3> --> + +<!-- <h3 id="windows">Windows</h3> --> + + +<!-- .................................................................. --> +<!-- <h2>Documentation improvements</h2> --> + + +<!-- .................................................................. --> +<!-- <h2 id="plugins">Improvements for plugin authors</h2> --> + +<!-- .................................................................. --> +<!-- <h2>Other significant improvements</h2> --> + + +<!-- .................................................................. --> +<!-- <h2><a name="11.1">GCC 11.1</a></h2> --> + +</body> +</html> diff --git a/htdocs/gcc-11/criteria.html b/htdocs/gcc-11/criteria.html new file mode 100644 index 00000000..cef92821 --- /dev/null +++ b/htdocs/gcc-11/criteria.html @@ -0,0 +1,153 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<title>GCC 11 Release Criteria</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" /> +</head> + +<body> + +<h1>GCC 11 Release Criteria</h1> + +<p>This page provides the release criteria for GCC 11.</p> + +<p>The GCC team (and, in particular, the Release Managers) will attempt +to meet these criteria before the release of GCC 11.</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 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.</p> + +<p>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.</p> + +<h1>Languages</h1> + +<p>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.</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 are:</p> +<ul> + +<li> +<p>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.</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 are:</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 general bugs blocking the release are marked with priority P1 +(<a href="../bugs/management.html">Maintaining the GCC Bugzilla database</a>).</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 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.</p> + +<h2>Primary Platform List</h2> + +<p>The primary platforms are:</p> +<ul> +<li>aarch64-none-linux-gnu</li> +<li>arm-linux-gnueabi</li> +<li>i586-unknown-freebsd</li> +<li>i686-pc-linux-gnu</li> +<li>mipsisa64-elf</li> +<li>powerpc64-unknown-linux-gnu</li> +<li>sparc-sun-solaris2.11</li> +<li>x86_64-pc-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 to +merit blocking the release.</p> + +</body> +</html> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 139 ++++++++++++++++++++++++++++++++ htdocs/{gcc-10 => gcc-11}/criteria.html | 8 +- 2 files changed, 143 insertions(+), 4 deletions(-) create mode 100644 htdocs/gcc-11/changes.html copy htdocs/{gcc-10 => gcc-11}/criteria.html (96%) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-04-30 15:50 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200430155058.7DCAB3898524@sourceware.org \ --to=jakub@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).