From: mrs@wrs.com (Mike Stump)
To: egcs@cygnus.com, schmid@ltoi.iap.physik.th-darmstadt.de
Subject: Re: testsuite results
Date: Mon, 13 Oct 1997 13:41:00 -0000 [thread overview]
Message-ID: <199710132015.NAA04846@kankakee.wrs.com> (raw)
> Date: Sun, 12 Oct 1997 19:44:51 +0200 (MEST)
> From: Peter Schmid <schmid@ltoi.iap.physik.th-darmstadt.de>
> To: egcs@cygnus.com
> 2. While compiling g++.mike/ambig1.C I get an recoverable compiler error.
> What is that?
Well, the general rule is to fix the first problem listed, and then
recompile. In this case, that is what should be done, though, since
this testcase just wants to generate error messages, of course, there
is no problem.
If you want a more complete description, imagine a compiler that could
detect when it was in error, then corrected it's problem before
screwing the user, and found a way to get the developers to fix the
underlying problem, to further enhance the compiler... Well, that is
what it does. In this case, since there was a prior error, it is less
meaningful, but in theory we could teach the compiler to recover from
the first error in a more complete way. Currently, it doesn't recover
from the first error as well as it should.
One might be tempted to call this software fault tolerance, personally
I think it is more useful than core dumping the compiler.
next reply other threads:[~1997-10-13 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-13 13:41 Mike Stump [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-11-29 3:01 Peter Schmid
[not found] <Pine.A32.3.95.971124095550.18831A-100000.cygnus.egcs@ltoi.iap.physik.tu-darmstadt.de>
1997-11-24 21:47 ` Jason Merrill
1997-11-25 11:44 ` Joe Buck
1997-11-25 19:10 ` Jeffrey A Law
1997-11-24 1:05 Peter Schmid
1997-10-26 7:12 Peter Schmid
1997-10-18 9:55 Peter Schmid
1997-10-12 10:44 Peter Schmid
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=199710132015.NAA04846@kankakee.wrs.com \
--to=mrs@wrs.com \
--cc=egcs@cygnus.com \
--cc=schmid@ltoi.iap.physik.th-darmstadt.de \
/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).