From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Sandiford <richard.sandiford@linaro.org>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix mult expansion ICE (PR middle-end/82875)
Date: Wed, 22 Nov 2017 10:16:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1711221108350.12252@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20171122095523.GK14653@tucnak>
On Wed, 22 Nov 2017, Jakub Jelinek wrote:
> On Wed, Nov 22, 2017 at 10:41:19AM +0100, Richard Biener wrote:
> > How much churn would it be to pass down a mode alongside the operands
> > in expand_binop? Can't find it right now but didn't we introduce
> > some rtx_with_mode pair-like stuff somewhen?
>
> We have rtx_mode_t for that. But there are 240+ calls to expand_binop,
> and even if we add an overload that will transform it, unless we forcefully
> inline it wouldn't that slow down all the spots a little bit?
> The thing is, for the vast majority of binary ops we don't need the operand
> modes, it is mainly comparisons, second arg of shifts/rotates and this
> widening case.
Ok, so maybe split expand_binop then to the class of cases where we do
need the mode and a class where we don't then?
We don't have to use rtx_mode_t we can just pass two arguments. Not
sure what is more convenient to use.
Anyway, this doesn't have to happen in stage3, just as a general
note on how I believe we changed things in other places. Richard S.
may remember more here.
Richard.
next prev parent reply other threads:[~2017-11-22 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 9:26 Jakub Jelinek
2017-11-22 9:43 ` Richard Biener
2017-11-22 10:09 ` Jakub Jelinek
2017-11-22 10:16 ` Richard Biener [this message]
2017-11-22 13:34 ` Richard Sandiford
2017-11-22 13:50 ` Jakub Jelinek
2017-11-22 9:55 ` Richard Sandiford
2017-12-04 7:01 ` [testsuite, committed] Require effective target alloca for pr82875.c Tom de Vries
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=alpine.LSU.2.20.1711221108350.12252@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.sandiford@linaro.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).