public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-bugs@gcc.gnu.org, haoxintu@gmail.com
Subject: Re: How GCC treats ice-on-invalid-code?
Date: Wed, 01 Jul 2020 10:05:53 +0200 [thread overview]
Message-ID: <2976657.y7V46JpDgB@polaris> (raw)
In-Reply-To: <20200630143847.GA3488494@redhat.com>
> It's fine to file these ice-on-invalid bugs, but don't be surprised if
> nobody has time to work on bugs that are only triggered by unrealistic
> garbage input.
Right, an ICE is a perfectly valid outcome for garbage input and there are
hundreds of assertions in the compiler precisely for this purpose.
--
Eric Botcazou
next prev parent reply other threads:[~2020-07-01 8:05 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 [this message]
2020-07-01 11:24 ` Richard Sandiford
2020-07-02 8:51 ` Eric Botcazou
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=2976657.y7V46JpDgB@polaris \
--to=ebotcazou@libertysurf.fr \
--cc=gcc-bugs@gcc.gnu.org \
--cc=haoxintu@gmail.com \
--cc=jwakely@redhat.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).