From: Richard Biener <rguenther@suse.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Enable ICE-after-error with -fchecking
Date: Mon, 09 Dec 2019 07:54:00 -0000 [thread overview]
Message-ID: <nycvar.YFH.7.76.1912090853020.5566@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20191206161453.GP3152@gate.crashing.org>
On Fri, 6 Dec 2019, Segher Boessenkool wrote:
> On Wed, Dec 04, 2019 at 05:26:25PM +0100, Jakub Jelinek wrote:
> > I'd fear people will use -fchecking and feel error-recovery bugs are then
> > more important because they no longer get the more user friendly message.
> > Can't we arrange for the emergency IL dump to happen in this case anyway?
>
> Does it not already happen? You need dump files enabled, of course.
No, the issue is that IL verification errors use "error" and thus
you trigger the ICE-after-error machinery which appearantly goes
a completely different path. And -fchecking doesn't "disable"
the ICE-after-error detection (which IMHO it should and what this
patch is about).
Richard.
prev parent reply other threads:[~2019-12-09 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 14:21 Richard Biener
2019-12-04 16:26 ` Jakub Jelinek
2019-12-05 8:22 ` Richard Biener
2019-12-06 16:14 ` Segher Boessenkool
2019-12-09 7:54 ` Richard Biener [this message]
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=nycvar.YFH.7.76.1912090853020.5566@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=segher@kernel.crashing.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).