From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>,
"William J. Schmidt" <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH][expmed] Calculate mult-by-const cost properly in mult_by_coeff_cost
Date: Mon, 20 Apr 2015 09:28:00 -0000 [thread overview]
Message-ID: <5534C69B.6070402@arm.com> (raw)
In-Reply-To: <552E86BD.60601@redhat.com>
On 15/04/15 16:41, Jeff Law wrote:
> On 04/14/2015 02:07 AM, Kyrill Tkachov wrote:
>> Hi Jeff,
>>
>> Thanks for looking at this.
>>
>> On 13/04/15 19:18, Jeff Law wrote:
>>> On 03/16/2015 04:12 AM, Kyrill Tkachov wrote:
>>>> Hi all,
>>>>
>>>> Eyeballing the mult_by_coeff_cost function I think it has a typo/bug.
>>>> It's supposed to return the cost of multiplying by a constant 'coeff'.
>>>> It calculates that by taking the cost of a MULT rtx by that constant
>>>> and comparing it to the cost of synthesizing that multiplication, and
>>>> returning
>>>> the cheapest. However, in the MULT rtx cost calculations it creates
>>>> a MULT rtx of two REGs rather than the a REG and the GEN_INT of coeff as
>>>> I would
>>>> expect. This patches fixes that in the obvious way.
>>>>
>>>> Tested aarch64-none-elf and bootstrapped on x86_64-linux-gnu.
>>>> I'm guessing this is stage 1 material at this point?
>>>>
>>>> Thanks,
>>>> Kyrill
>>>>
>>>> 2015-03-13 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>>>>
>>>> * expmed.c (mult_by_coeff_cost): Pass CONT_INT rtx to MULT cost
>>>> calculation rather than fake_reg.
>>> I'm pretty sure this patch is wrong.
>>>
>>> The call you're referring to is computing an upper limit to the cost for
>>> use by choose_mult_variant. Once a synthesized multiply sequence
>>> exceeds the cost of reg*reg, then that synthesized sequence can be
>>> thrown away because it's not profitable.
>> But shouldn't the limit be the mult-by-constant cost?
> No, because ultimately we're trying to do better than just loading the
> constant into a register and doing a reg * reg. So the reg*reg case is
> the upper bound for allowed cost of a synthesized sequence.
So I've thought about it a bit more and I have another concern.
The function returns this:
if (choose_mult_variant (mode, coeff, &algorithm, &variant, max_cost))
return algorithm.cost.cost;
else
return max_cost;
If I read this right, it tries to synthesise the mult at choose_mult_variant
with the limit cost of the reg-by-reg mult, but if the synthesis cost exceeds
that, then it returns the reg-by-reg mult cost (in return max_cost;) so that
can't be right, can it?
Thanks,
Kyrill
>
>> Consider also similar logic in expand_mult:
>> max_cost = set_src_cost (gen_rtx_MULT (mode, fake_reg, op1), speed);
>> if (choose_mult_variant (mode, coeff, &algorithm, &variant, max_cost))
>> return expand_mult_const (mode, op0, coeff, target,
>> &algorithm, variant);
> This looks wrong to me. They're certainly inconsistent.
>
> Maybe start by asking Bill (who added mult_by_coeff_cost and whom I've
> cc'd) what his intent was to make sure it matches my understanding.
>
> Jeff
>
next prev parent reply other threads:[~2015-04-20 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 10:13 Kyrill Tkachov
2015-03-17 19:11 ` Jeff Law
2015-03-18 9:06 ` Kyrill Tkachov
2015-03-18 9:36 ` Bin.Cheng
2015-03-18 9:39 ` Kyrill Tkachov
2015-04-13 18:18 ` Jeff Law
2015-04-14 8:07 ` Kyrill Tkachov
2015-04-15 15:42 ` Jeff Law
2015-04-15 15:47 ` Kyrill Tkachov
2015-04-20 9:28 ` Kyrill Tkachov [this message]
2015-04-20 17:51 ` Jeff Law
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=5534C69B.6070402@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=wschmidt@linux.vnet.ibm.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).