From: Eric Botcazou <ebotcazou@adacore.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org, Kelvin Nilsen <kdnilsen@linux.vnet.ibm.com>
Subject: Re: [PATCH] PR80101: Fix ICE in store_data_bypass_p
Date: Fri, 07 Apr 2017 08:39:00 -0000 [thread overview]
Message-ID: <2042575.QfhRid7aWy@polaris> (raw)
In-Reply-To: <20170407074824.GU4402@gate.crashing.org>
> Or we could just change "blockage" and wait for the next bug report.
That's my suggestion, yes.
> Alternatively, we can arrange for the bypass functions to not ICE. We
> can do that specific to these rs6000 pipeline descriptions, by having
> our own version of store_data_bypass_p; or we can make that function
> work for all insns (its definition works fine for insn pairs where
> not both the producer and consumer are SETs). That's what Kelvin's
> patch does. What is the value in ICEing here?
Telling the back-end writer that something may be wrong somewhere instead of
silently accepting nonsense? How long have all the assertions been there?
--
Eric Botcazou
next prev parent reply other threads:[~2017-04-07 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 15:22 Kelvin Nilsen
2017-04-06 20:05 ` Eric Botcazou
2017-04-06 20:29 ` Segher Boessenkool
2017-04-07 6:54 ` Eric Botcazou
2017-04-07 7:48 ` Segher Boessenkool
2017-04-07 8:39 ` Eric Botcazou [this message]
2017-04-07 9:19 ` Segher Boessenkool
2017-04-10 17:38 ` Richard Sandiford
2017-04-10 21:37 ` Segher Boessenkool
2017-04-18 20:21 ` Eric Botcazou
2017-04-19 20:33 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2017-03-29 18:07 Kelvin Nilsen
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=2042575.QfhRid7aWy@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kdnilsen@linux.vnet.ibm.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).