[Bug target/85665] Multiple typos in diagnostics

[joseph at codesourcery dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665

--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Sun, 6 May 2018, roland.illig at gmx dot de wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665
> 
> --- Comment #3 from Roland Illig <roland.illig at gmx dot de> ---
> (In reply to Jonathan Wakely from comment #2)
> > It might be better to report multiple bugs, one per target backend, so that
> > the relevant target maintainers are informed.
> 
> Oh, I tried that last year. Of the 113 bugs I reported, 41 are still open.
> Therefore I thought I'd try a different approach this time.

Having separate bugs means it's possible to tell what's resolved and 
what's not.  With an omnibus bug you'd have a bug reporting 113 issues of 
which 41 are unresolved and no way for anyone to tell what's open and 
what's resolved without a lot of work (thus, no way for someone to quickly 
find and fix an issue from the open bug).  (To track separate bugs it can 
be useful to have either a keyword for such typos in diagnostics, or a 
meta-bug depending on all such bugs.)

But, yes, sending patches to gcc-patches and the relevant maintainers (and 
getting write access so you can commit typo fixes as obvious) may be 
helpful.