From patchwork Sat Aug 25 10:54:00 2018
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Gerald Pfeifer A good bug report, which is complete and self-contained, enables us
to fix the bug. After this summary, you'll find detailed instructions that explain
how to obtain some of the information requested in this summary. Please include all of the following items, the first
three of which can be obtained from the output of Please submit your bug report directly to the
GCC bug tracker.
@@ -136,7 +136,7 @@
this. We apologize for the inconvenience.
Please refer to the next section when reporting
bugs in GNAT, the Ada compiler, or to the one after
@@ -176,7 +176,7 @@
the body of your bug report as plain text, even if needlessly
duplicated as part of an archive. See the previous section for bug reporting
instructions for GCC language implementations other than Ada. There are many reasons why a reported bug doesn't get fixed.
It might be difficult to fix, or fixing it might break compatibility.
@@ -259,7 +259,7 @@
The following are not actually bugs, but are reported often
enough to warrant a mention here. Most C++ compilers (G++ included) do not yet implement
@@ -657,7 +657,7 @@
Bugzilla offers a number of different fields. From a maintainer's
perspective, these are the relevant ones and what their values mean: The following two fields describe how serious a bug is from a user's
perspective (Severity) and what Priority we assign to it in fixing it:
-Reporting Bugs
+Reporting Bugs
What we need
+What we need
gcc -v
:What we do not want
+What we do not want
-#include
s header files that are left
@@ -122,7 +122,7 @@
dedicated to the discussion of the programming languageWhere to post it
+Where to post it
Detailed bug reporting instructions
+Detailed bug reporting instructions
Detailed bug reporting instructions for GNAT
+Detailed bug reporting instructions for GNAT
-Frequently Reported Bugs
+Frequently Reported Bugs
-Non-bugs
+Non-bugs
-General
+General
-C
+C
++
/--
) not
@@ -534,7 +534,7 @@
-C++
+C++
-Common problems when upgrading the compiler
+Common problems when upgrading the compiler
ABI changes
Index: management.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.36
diff -u -r1.36 management.html
--- management.html 2 Jun 2018 21:16:12 -0000 1.36
+++ management.html 25 Aug 2018 10:25:49 -0000
@@ -57,7 +57,7 @@
Status
+Status
The status and resolution fields define and track the life cycle of a
bug. In addition to their
-Importance (Severity and Priority)
+Importance (Severity and Priority)
This is the person in charge of resolving the bug. Every time this field changes, the status changes to NEW to make it easy to see @@ -178,7 +178,7 @@ This makes sure that all NEW reports are really analyzed and are ready to be handed off to the people actually fixing bugs.
-Regressions should be explicitly +
Regressions should be explicitly marked as such. The summary line should read