public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Reshabh K Sharma <reshabh@cs.washington.edu>
Cc: Jeff Law <jeffreyalaw@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: Describe instructions with same reg in def and use or mutiple defs and attach write latency
Date: Thu, 3 Feb 2022 19:31:56 -0600	[thread overview]
Message-ID: <20220204013156.GD614@gate.crashing.org> (raw)
In-Reply-To: <CAAhFPT1w5ddYgqG93vv7LvAVVjBXYdduepFJ2Gx7tRzpgKjoMA@mail.gmail.com>

Hi!

On Thu, Feb 03, 2022 at 05:06:23PM -0800, Reshabh K Sharma wrote:
> On Fri, Jan 28, 2022 at 10:23 AM Segher Boessenkool <
> segher@kernel.crashing.org> wrote:
> > You can use TARGET_SCHED_ADJUST_COST?
> 
> Thank you so much! I think target_sched_adjust_cost will do.
> Given two rtx_insn,
> x = exp_load addr offset and
> y = add addr z,
> these two instructions are the input arguments to target_sched_adjust_cost,
> 
> how do I check that given rtx_insn is exp_load? (how do we check if
> rtx_insn is of type exp_load, add or any other target specific instruction?)
> and how do I check if there is a read after read dependency for addr
> operand and not the offset.

"type" is just an insn attribute, so you would use
  if (get_attr_type (insn) == TYPE_EXP_LOAD)
or similar.


Segher

  reply	other threads:[~2022-02-04  1:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  1:20 Reshabh K Sharma
2022-01-28 17:39 ` Jeff Law
2022-01-28 18:21   ` Segher Boessenkool
2022-02-04  1:06     ` Reshabh K Sharma
2022-02-04  1:31       ` Segher Boessenkool [this message]
2022-02-16 19:41         ` Reshabh K Sharma
2022-02-17 18:48           ` 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=20220204013156.GD614@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=reshabh@cs.washington.edu \
    /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).