public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: richard.sandiford@arm.com
Cc: Jonathan Wakely <jwakely@redhat.com>,
gcc-bugs@gcc.gnu.org, haoxintu@gmail.com
Subject: Re: How GCC treats ice-on-invalid-code?
Date: Thu, 02 Jul 2020 10:51:23 +0200 [thread overview]
Message-ID: <4346527.u1zSKOHnED@polaris> (raw)
In-Reply-To: <mpto8oztr4k.fsf@arm.com>
> You mean, an ICE is perfectly valid as the first (and obviously then
> only) error diagnostic the compiler prints for “garbage input”?
> If so, I don't think that's true. What counts as “garbage” seems
> a bit too subjective for that anyway.
When the input is totally nonsensical, e.g. generated by a machine for the
sole purpose of torturing the compiler, an ICE is good enough and IMO the bug
report should essentially be ignored. We have hundreds of open bug reports
for perfectly sensible code and any of them should have higher priority.
> E.g. deleting a chunk of lines from a file creates something that makes
> no sense and might be considered garbage, but that can easily happen
> with a botched resolution to a merge conflict (or being too trigger-happy
> with git rerere :-)). I don't think it's OK for the compiler simply to
> crash without first giving the user an idea of what's wrong.
Sure, if the input originally comes from a real program, it's not garbage.
--
Eric Botcazou
prev parent reply other threads:[~2020-07-02 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 2:32 Haoxin Tu
2020-06-30 3:09 ` Haoxin Tu
2020-06-30 14:28 ` Jonathan Wakely
2020-06-30 13:22 ` Richard Sandiford
2020-06-30 14:38 ` Jonathan Wakely
2020-07-01 8:05 ` Eric Botcazou
2020-07-01 11:24 ` Richard Sandiford
2020-07-02 8:51 ` Eric Botcazou [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=4346527.u1zSKOHnED@polaris \
--to=ebotcazou@libertysurf.fr \
--cc=gcc-bugs@gcc.gnu.org \
--cc=haoxintu@gmail.com \
--cc=jwakely@redhat.com \
--cc=richard.sandiford@arm.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).