Re: Suggestions for GNATS

[Richard Earnshaw <rearnsha at arm dot com>]

> Richard Earnshaw wrote:-
> 
> > I'd also like to see the "target" category sub-divided into target-<cpu> 
> > (where, say, cpu is the name of the directory in gcc/config).  This would 
> > enable me to find reports for the ARM in a much more reliable manner (at 
> > present a gnats search for the string "arm" returns about 9 false matches 
> > for every true one (since it finds things like "parm").
> 
> Yes, that would suit me instead of the "hardware" thing.  For e.g. x86,
> it should contain the general "x86" meaning any "x86", and then maybe
> x386, x486, x586, x686 - the latter in particular often needs to be
> distinguished from the others.

Isn't that overkill?  Don't forget we have to list each category in 
gccbug.  Once you have target/x86 searching in that for strings such as 
x568 should not be hard.

BTW  Having tried to use gccbug, I think it is a mess.  There are so many 
comments that it's impossible to quickly find the fields that need 
completing for those who have used it before (and it's not clear to me 
that a novice would even be able to tell what was a comment and what was a 
field.

Can't we find a way to make it clearer?  Some blank lines between each 
section of comments?  Indent SEND-PR: a bit (so that the fields are the 
only items starting in column 1?

Eg:

>Submitter-Id:	net
>Originator:	

>Organization:	<organization of PR author (multiple lines)>

>Confidential:	no
  SEND-PR: Leave "Confidential" as "no"; all GCC PRs are public.

>Synopsis:	<synopsis of the problem (one line)>

>Severity:	<[ non-critical | serious | critical ] (one line)>
  SEND-PR: critical     GCC is completely not operational...
  SEND-PR: serious      GCC is not working properly; a work-...
  SEND-PR: non-critical Report indicates minor problem.