Michael Veksler <[EMAIL PROTECTED]> wrote:
> Unfortunately, this is not 100% correct. Recently I have filed several
> duplicates, *after* searching Bugzilla.
That is not a problem. Bugmasters are there exactly for that. We realize that
finding duplicates can be very hard (in fact, sometimes duplicates are
acknowledged as such only after a fix appears), so that is our work. We just
ask users for some *basic* duplicate checking, and I think most users do that
before filing bugreports. So it's ok.
> 3. Nontrivial search of GCC Bugzilla are, sometimes,
> extremely slow (over a minute).
3 could be worked on (Daniel?)
> Technically speaking, these are not GCC bugs. However, from
> user's POV they *are* GCC bugs. This mismatch between user
> and developer perceptions is not very healthy and may inhibit
> other PRs. Maybe developers should be more open to "fixing"
> things that are not purely GCC bugs?
Maybe. But I don't think people don't file bugreports because of this. In every
software company I have been working on there has always been some debates
about bugreports ("it's your code's fault" -- "no, it's yours"), I expect GCC
users to know/expect this. Anyway, we are speaking of a really minority of the
bug reports we get. Most of the bugreports filed *are* related to GCC, and
among those that are not, most are *obviously* so (in that, people realize
immediately it's not GCC's fault).
> [2] GCC could implement a better error message.
This is a bug, too. You can file a PR in Bugzilla explictly asking for a more
informative error message.
Giovanni Bajo
