This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Future of gccbug


On  7 Nov, Rainer Orth wrote:
> Volker Reichelt <reichelt@igpm.rwth-aachen.de> writes:
> 
>> apart from PR 12900 we haven't had any submissions of PRs via gccbug in
>> the last couple of months (according to Daniel's statistics).
> 
> I doubt that: I've submitted a couple in September, October and just
> November 4th (with more to come).

Hmmm. Seems like the statistics are incorrect.

>> This raises the question: Should the 3.4 release really contain this
>> script? Or should we rather rip it out now to simplify maintenance?
> 
> Where's the maintenance burden for that script?  It just works, the
> infrastructure for conversion to bugzilla is in place, and it's used by at
> least a couple of users.
>
> Why break this when there's no gain but a unsubstantiated claim of
> `simplified maintenance'?  This has been discussed before, and I can only
> point out the importance of offline bug submission and proper bug report
> formatting/editing.

Well, the bugzilla interface slowly diverges from gccbug, since nobody
does the maintenance. A quick glace at the code of gccbug gives:

SEND-PR: doc-bug          The documentation is incorrect.
SEND-PR: accepts-illegal  GCC fails to reject erroneous code.
SEND-PR: rejects-legal    GCC gives an error message for correct code.
SEND-PR: wrong-code       The machine code generated by gcc is incorrect.
SEND-PR: ice-on-legal-code   GCC gives an Internal Compiler Error (ICE)
SEND-PR:                     for correct code
SEND-PR: ice-on-illegal-code GCC gives an ICE instead of reporting an error
SEND-PR: pessimizes-code     GCC misses an important optimization opportunity
SEND-PR: sw-bug              Software bug of some other class than above
SEND-PR: change-request      A feature in GCC is missing.
SEND-PR: support             I need help with gcc.

This is quite different from the set of keywords we do have in bugzilla.
So I doubt "proper bug report formatting/editing" with gccbug.

We're close to extracting the relavant information out of
gccbug-submissions by hand, because the automatic conversion
cannot do this job. And at that point I don't see much difference
between gccbug and plain mail.

Regards,
Volker



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]