This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Suggestions for GNATS
- To: Joe Buck <jbuck at synopsys dot COM>
- Subject: Re: Suggestions for GNATS
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Wed, 28 Feb 2001 11:53:56 +0000
- cc: neil at daikokuya dot demon dot co dot uk (Neil Booth), gcc at gcc dot gnu dot org, pfeifer at dbai dot tuwien dot ac dot at (Gerald Pfeifer), Richard dot Earnshaw at arm dot com
- Organization: ARM Ltd.
- Reply-To: Richard dot Earnshaw at arm dot com
>
> > One of my complaints is that a lot of reports get dumped into the
> > catch-all categories of "c" and "c++" for no reason other than the code
> > being compiled is c / c++. I'd like to rename these "C front end" and
> > "C++ front end" respectively, to make (what I assume) is the intended
> > meaning more clear.
>
> Users may not be able to distinguish front end from back end bugs, so
> any such process will have to involve bug reviewers re-classifying them
> later on.
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, we get mis-categorized reports, but it isn't a major task to
recategorize a report.
R.