From: Segher Boessenkool <segher@kernel.crashing.org>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ping #4][patch] Fix PR80929: Realistic PARALLEL cost in seq_cost.
Date: Wed, 12 Jul 2017 19:36:00 -0000 [thread overview]
Message-ID: <20170712193605.GQ13471@gate.crashing.org> (raw)
In-Reply-To: <48a6d282-a3b2-99da-e190-9bba101ae2ec@gjlay.de>
On Wed, Jul 12, 2017 at 03:30:00PM +0200, Georg-Johann Lay wrote:
> On 12.07.2017 14:11, Segher Boessenkool wrote:
> >On Tue, Jul 11, 2017 at 10:47:27AM +0200, Georg-Johann Lay wrote:
> >>This small addition improves costs of PARALLELs in
> >>rtlanal.c:seq_cost(). Up to now, these costs are
> >>assumed to be 1 which gives gross inexact costs for,
> >>e.g. divmod which is represented as PARALLEL.
> >
> >insn_rtx_cost returns 0 ("unknown") for such a PARALLEL, so your
> >current patch does not change this at all?
>
> Huh? It returns the costs of 1st SET in a PARALLEL (provided it
> has one), no? Or even costs for come compares.
No, it returns 0 if there is more than one normal SET (or more than
one compare).
> >>+ else if (INSN_P (seq)
> >>+ && PARALLEL == GET_CODE (PATTERN (seq)))
> >
> >Yoda conditions have we should not.
>
> hmm, I didn't find something like PARALLEL_P (rtx).
> Is comparing rtx_codes deprecated now?
I meant it should be written
else if (INSN_P (seq) && GET_CODE (PATTERN (seq)) == PARALLEL)
i.e. constant on the right.
> >This whole thing could be something like
> >
> > if (INSN_P (seq))
> > {
> > int t = insn_rtx_cost (PATTERN (seq), speed);
>
> This will behave differently.
Yes, I know, I even said so.
> >(Why do you need a check for INSN_P here? Why does it increment the
>
> >cost for non-insns? So many questions).
>
> Again, you'll have to ask the original author for reasoning.
Since you want to change the code, to make it better, I was hoping
you would dig in a bit. To make it better, not just different :-/
Segher
next prev parent reply other threads:[~2017-07-12 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 8:47 Georg-Johann Lay
2017-07-12 12:11 ` Segher Boessenkool
2017-07-12 13:30 ` Georg-Johann Lay
2017-07-12 19:36 ` Segher Boessenkool [this message]
2017-07-13 11:04 ` Georg-Johann Lay
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=20170712193605.GQ13471@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=avr@gjlay.de \
--cc=gcc-patches@gcc.gnu.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).