public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "igodard at pacbell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/23281] New: Miscategorization of quality-of-implementation reports
Date: Mon, 08 Aug 2005 02:41:00 -0000	[thread overview]
Message-ID: <20050808024133.23281.igodard@pacbell.net> (raw)

This DR reflects bug report #23263 (q.v.) but addresses a larger issue. That
report has been categorized as an "enhancement request". 

Should this and other reports about diagnostic quality be treated as
"enhancement requests"? I suppose tht it depends on what you consider
"correctness". If correctness means "conforming to standard", then any
diagnostic will do, including "something wrong found somewhere in program".
Personally I use a different standard of "correct", which includes "usable", and
so addresses issues like compilation time measured in days as well as quality of
diagnostic.

I understand that the gcc implementation community has a notion of "QOI"
(quality of implementation) which reflects much of what I call "usable". But I
would distinguish a "defect of QOI" from an "enhancement request"; the latter
being something nice to have, but the former impacting real usage.

I put this particular DR (#23262) in the "defect of QOI" category. Even if you
do not, you probably can select a non-empty set of DRs that are truly "defects"
and not mere "enhancement requests. 

Consequently I'm filing this DR against the gcc DR reporting machinery itself,
rather than against the compiler in particular. There needs to be categories for
QOI defects of varying severity; either that, or complaints about diagnostics
and other QOI ussues should not by policy be filed as "enhancement requests",
and forgotten.

-- 
           Summary: Miscategorization of quality-of-implementation reports
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: igodard at pacbell dot net
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23281


             reply	other threads:[~2005-08-08  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08  2:41 igodard at pacbell dot net [this message]
2005-08-08  2:48 ` [Bug other/23281] " pinskia at gcc dot gnu dot org
2005-08-08  3:00 ` dberlin at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050808024133.23281.igodard@pacbell.net \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).