From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/5] Rename existing insn_cost to insn_sched_cost
Date: Wed, 02 Aug 2017 16:36:00 -0000 [thread overview]
Message-ID: <c6b19e85-90e2-c1f3-43b6-aac1f3f25056@redhat.com> (raw)
In-Reply-To: <47f2b82b6ca71095500881627ed3c25ae01d15d4.1501541006.git.segher@kernel.crashing.org>
On 07/31/2017 05:25 PM, Segher Boessenkool wrote:
> haifa-sched exports an insn_cost function, but it is only used in a
> few places and specialised to scheduling. This patch renames it to
> insn_sched_cost.
>
> ---
> gcc/haifa-sched.c | 14 +++++++-------
> gcc/sched-int.h | 2 +-
> gcc/sched-rgn.c | 4 ++--
> gcc/sel-sched-ir.c | 2 +-
> 4 files changed, 11 insertions(+), 11 deletions(-)
This seems fine independent of the following patches. So with a
ChangeLog it should probably go in now rather than later.
jeff
next prev parent reply other threads:[~2017-08-02 16:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 0:15 [PATCH 0/5] RFC, WIP: RTL cost improvements 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 [this message]
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
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=c6b19e85-90e2-c1f3-43b6-aac1f3f25056@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).