public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "Hurugalawadi, Naveen" <Naveen.Hurugalawadi@cavium.com>,
	Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "Pinski, Andrew" <Andrew.Pinski@cavium.com>,
	"roland.illig@gmx.de" <roland.illig@gmx.de>,
	"joseph@codesourcery.com" <joseph@codesourcery.com>,
	"dmalcolm@redhat.com" <dmalcolm@redhat.com>, nd <nd@arm.com>,
	James Greenhalgh <james.greenhalgh@arm.com>,
	Marcus Shawcroft <marcus.shawcroft@arm.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
	"ramana.radhakrishnan@foss.arm.com"
	<ramana.radhakrishnan@foss.arm.com>
Subject: Re: [PING][PATCH] Move the check for any_condjump_p from sched-deps to target macros
Date: Thu, 27 Apr 2017 17:42:00 -0000	[thread overview]
Message-ID: <675f27f3-2ea4-2c0b-84f2-c92c1289fbaf@redhat.com> (raw)
In-Reply-To: <CO2PR07MB26946376EB24A0EB2BB66C6583110@CO2PR07MB2694.namprd07.prod.outlook.com>

On 04/26/2017 06:50 AM, Hurugalawadi, Naveen wrote:
> Hi Wilco,
> 
> Thanks for reviewing the patch.
> 
>>> The return false seems incorrect - it means a core can either have
>>> FUSE_CMP_BRANCH or FUSE_ALU_BRANCH but not both.
> Thanks for pointing out about the confusion.
> Modified the code as required.
> 
> Bootstrapped and Regression tested on AArch64 and X86_64.
> Please review the patch and let us know if its okay?
> 
> Thanks,
> Naveen
> 
> 
> fusion-anycond-jump-1.patch
> 
> 
> diff --git a/gcc/sched-deps.c b/gcc/sched-deps.c
> index b2393bf..b15a865 100644
> --- a/gcc/sched-deps.c
> +++ b/gcc/sched-deps.c
> @@ -2835,33 +2835,16 @@ sched_macro_fuse_insns (rtx_insn *insn)
>   {
>     rtx_insn *prev;
>   
> -  if (any_condjump_p (insn))
> -    {
> -      unsigned int condreg1, condreg2;
> -      rtx cc_reg_1;
> -      targetm.fixed_condition_code_regs (&condreg1, &condreg2);
> -      cc_reg_1 = gen_rtx_REG (CCmode, condreg1);
> -      prev = prev_nonnote_nondebug_insn (insn);
> -      if (!reg_referenced_p (cc_reg_1, PATTERN (insn))
> -          || !prev
> -          || !modified_in_p (cc_reg_1, prev))
> -        return;
> -    }
> -  else
> -    {
> -      rtx insn_set = single_set (insn);
> -
> -      prev = prev_nonnote_nondebug_insn (insn);
> -      if (!prev
> -          || !insn_set
> -          || !single_set (prev))
> -        return;
> +  rtx insn_set = single_set (insn);
>   
> -    }
> +  prev = prev_nonnote_nondebug_insn (insn);
> +  if (!prev
> +      || !insn_set
> +      || !single_set (prev))
> +    return;
>   
>     if (targetm.sched.macro_fusion_pair_p (prev, insn))
>       SCHED_GROUP_P (insn) = 1;
> -
>   }
Doesn't this avoid calling the target hook in cases where it used to 
call it before?

Consider a conditional jump inside a parallel that is not a single set.

Previously that could call the target hook and potentially set 
SCHED_GROUP_P.  But after your change I think it would return without 
ever querying the backend.

jeff

  parent reply	other threads:[~2017-04-27 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  4:57 [PATCH] " Hurugalawadi, Naveen
2017-04-25  7:40 ` [PING][PATCH] " Hurugalawadi, Naveen
2017-04-25 11:39   ` Wilco Dijkstra
2017-04-26 12:58     ` Hurugalawadi, Naveen
     [not found]       ` <AM5PR0802MB2610E2BBB884B9FD27734AA683110@AM5PR0802MB2610.eurprd08.prod.outlook.com>
2017-04-27  7:29         ` Hurugalawadi, Naveen
2017-04-27 17:42       ` Jeff Law [this message]
2017-05-11  4:47         ` Hurugalawadi, Naveen
2017-05-26  6:22           ` [PING 2][PATCH] " Hurugalawadi, Naveen
2017-05-26 11:35             ` Wilco Dijkstra
2017-06-14 10:27               ` [PING 3][PATCH] " Hurugalawadi, Naveen
2017-06-23 15:39           ` [PING][PATCH] " Jeff Law
2017-06-27  4:20             ` Hurugalawadi, Naveen
2017-06-29 15:00               ` 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=675f27f3-2ea4-2c0b-84f2-c92c1289fbaf@redhat.com \
    --to=law@redhat.com \
    --cc=Andrew.Pinski@cavium.com \
    --cc=Naveen.Hurugalawadi@cavium.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=james.greenhalgh@arm.com \
    --cc=joseph@codesourcery.com \
    --cc=marcus.shawcroft@arm.com \
    --cc=nd@arm.com \
    --cc=ramana.radhakrishnan@foss.arm.com \
    --cc=roland.illig@gmx.de \
    /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).