From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>,
gcc-patches@gcc.gnu.org, richard.sandiford@linaro.org
Subject: Re: [PATCH 0/5] RFC, WIP: RTL cost improvements
Date: Wed, 09 Aug 2017 17:12:00 -0000 [thread overview]
Message-ID: <20170809171213.GW13471@gate.crashing.org> (raw)
In-Reply-To: <878tis8ywf.fsf@linaro.org>
On Wed, Aug 09, 2017 at 05:54:40PM +0100, Richard Sandiford wrote:
> Segher Boessenkool <segher@kernel.crashing.org> writes:
> > We need it, for example, to properly cost the various define_insn_and_split
> > (for which "type" is only an approximation, and is woefully inadequate
> > for determining cost).
>
> But define_insn_and_splits could override the cost explicitly if they
> need to. That seems neater than testing for them in C.
All 190 of them? Not counting those that are define_insn+define_split
(we still have way too many of those).
Neat, indeed, but not altogether practical :-(
Segher
WARNING: multiple messages have this Message-ID
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>,
gcc-patches@gcc.gnu.org, richard.sandiford@linaro.org
Subject: Re: [PATCH 0/5] RFC, WIP: RTL cost improvements
Date: Wed, 09 Aug 2017 18:18:00 -0000 [thread overview]
Message-ID: <20170809171213.GW13471@gate.crashing.org> (raw)
Message-ID: <20170809181800.Qxt9ijMnrXzZkXvyyFEFJpr_o_0jxYclke6LCgu8tjE@z> (raw)
In-Reply-To: <878tis8ywf.fsf@linaro.org>
On Wed, Aug 09, 2017 at 05:54:40PM +0100, Richard Sandiford wrote:
> Segher Boessenkool <segher@kernel.crashing.org> writes:
> > We need it, for example, to properly cost the various define_insn_and_split
> > (for which "type" is only an approximation, and is woefully inadequate
> > for determining cost).
>
> But define_insn_and_splits could override the cost explicitly if they
> need to. That seems neater than testing for them in C.
All 190 of them? Not counting those that are define_insn+define_split
(we still have way too many of those).
Neat, indeed, but not altogether practical :-(
Segher
next prev parent reply other threads:[~2017-08-09 17:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 0:15 Segher Boessenkool
2017-08-01 0:05 ` [PATCH 2/5] Replace insn_rtx_cost with insn_cost and pattern_cost Segher Boessenkool
2017-08-02 16:38 ` Jeff Law
2017-08-01 0:05 ` [PATCH 3/5] combine: Use insn_cost instead of pattern_cost everywhere Segher Boessenkool
2017-08-02 16:40 ` Jeff Law
2017-08-02 21:23 ` Segher Boessenkool
2017-08-01 0:05 ` [PATCH 4/5] Add targetm.insn_cost hook Segher Boessenkool
2017-08-02 16:39 ` Jeff Law
2017-08-01 0:15 ` [PATCH 1/5] Rename existing insn_cost to insn_sched_cost Segher Boessenkool
2017-08-02 16:36 ` Jeff Law
2017-08-01 0:15 ` [PATCH 5/5] rs6000: Implement insn_cost hook Segher Boessenkool
2017-08-01 9:07 ` [PATCH 0/5] RFC, WIP: RTL cost improvements Richard Biener
2017-08-05 10:07 ` Richard Sandiford
2017-08-05 17:15 ` Segher Boessenkool
2017-08-08 16:41 ` Jeff Law
2017-08-08 16:55 ` Richard Sandiford
2017-08-09 15:56 ` Jeff Law
2017-08-09 16:19 ` Richard Sandiford
2017-08-09 16:40 ` Segher Boessenkool
2017-08-09 16:54 ` Richard Sandiford
2017-08-09 17:12 ` Segher Boessenkool [this message]
2017-08-09 18:18 ` Segher Boessenkool
2017-08-10 7:18 ` Richard Sandiford
2017-08-09 16:57 ` Segher Boessenkool
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=20170809171213.GW13471@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@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).