This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Prototype of a --report-bug option
- From: Yury Gribov <y dot gribov at samsung dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>, David Malcolm <dmalcolm at redhat dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Maxim Ostapenko <m dot ostapenko at partner dot samsung dot com>
- Date: Wed, 30 Jul 2014 18:42:41 +0400
- Subject: Re: Prototype of a --report-bug option
- Authentication-results: sourceware.org; auth=none
- References: <1406658940 dot 2134 dot 113 dot camel at surprise> <CAFiYyc3Y=OHHN9rJf5V3dWvsRMxUzxfC=si8K3cy+sr2NYh0EQ at mail dot gmail dot com>
On 07/30/2014 11:56 AM, Richard Biener wrote:
On Tue, Jul 29, 2014 at 8:35 PM, David Malcolm<dmalcolm@redhat.com> wrote:
>At Cauldron on the Sunday morning there was a Release Management BoF
>session, replacing the specRTL talk (does anyone know what happened to
>the latter?)
>
>One of the topics was bug triage, and how many bug reports lacked basic
>metadata on e.g. host/build/target, reproducer etc.
>
Heh... I was hoping this would be a patch to the driver directly
(thus not a python script). Note that I don't care too much about
the reproducing/-save-temps and backtrace for the driver option.
Of course in case of an ICE producing a proper bug-url with the
backtrace info included would even be better.
All, we've been trying to upstream a patch for something like this for
last month.
It doesn't bring you to Bugzilla but at least generates a repro
with host/target information and call stack. Could someone take a look?
We could certainly enhance it to generate user-friendly links like in
David's script.
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg01649.html
-Y