From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: GNATS policy question
Date: Fri, 13 Dec 2002 01:31:00 -0000 [thread overview]
Message-ID: <200212130953.KAA51568@numa6.igpm.rwth-aachen.de> (raw)
In-Reply-To: <6670000.1039713413@warlock.codesourcery.com>
On 12 Dec, Mark Mitchell wrote:
>
>
> --On Thursday, December 12, 2002 10:48:03 AM +0100 Volker Reichelt
> <reichelt@igpm.rwth-aachen.de> wrote:
>
>> On 11 Dec, Mark Mitchell wrote:
>>
>>>> What's the GNATS policy about PRs that issue an ICE in development
>>>> versions and a "confused by earlier errors, bailing out" message in
>>>> release versions?
>>>
>>> We should mark those PRs medium-priority.
>>>
>>> GCC simply doesn't have a coherent design for error-recovery, and until
>>> it does the set of places where we crash after error messages will move
>>> around from time to time, hopefully shrinking over time. I have ideas
>>> about this, but not enough time to implement them ...
>>
>> Shouldn't we suspend those PRs then? We could add "[error-recovery]" to
>> the synopsis line. Maybe some of the PRs will be fixed with the new
>> parser, so IMHO we should suspend them till the new parser arrives
>> anyway before spending too much effort on them.
>
> It's very hard to say where the problems are. Some might be fixed by the
> new parser. Others need error recovery code in the front ends. I think
> it's OK to keep them open -- they *are* defects. Just not very important
> ones. Maybe mark them low priority?
Low priority sounds good to me.
Three final questions:
* Should we add "[error-recovery]" to the synopsis line so that one does
not stumble over those bugs over and over again?
* Shall I prepare a patch for the policies section of gnatswrite.html
to document the procedure?
* There are some bugs in GNATS that were closed because a "confused by
earlier ..." message was issued. Shall I reopen them?
Regards,
Volker
next prev parent reply other threads:[~2002-12-13 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 8:01 Volker Reichelt
2002-12-11 22:33 ` Mark Mitchell
2002-12-12 3:35 ` Volker Reichelt
2002-12-12 10:08 ` Mark Mitchell
2002-12-13 1:31 ` Volker Reichelt [this message]
2002-12-13 8:39 ` Mark Mitchell
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=200212130953.KAA51568@numa6.igpm.rwth-aachen.de \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).