public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] rtl-optimization/109237 - speedup bb_is_just_return
Date: Tue, 28 Mar 2023 09:49:12 +0200	[thread overview]
Message-ID: <ZCKb+Cd8FG8CGugo@tucnak> (raw)
In-Reply-To: <20230322100356.5B99E3857C48@sourceware.org>

On Wed, Mar 22, 2023 at 10:03:42AM +0000, Richard Biener via Gcc-patches wrote:
> For the testcase bb_is_just_return is on top of the profile, changing
> it to walk BB insns backwards puts it off the profile.  That's because
> in the forward walk you have to process possibly many debug insns
> but in a backward walk you very likely run into control insns first.
> 
> Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
> 
> OK?
> 
> For the record, the profile was (after the delete_trivially_dead_insns 
> fix)
> 
> Samples: 289K of event 'cycles:u', Event count (approx.): 384226334976                      
> Overhead       Samples  Command  Shared Object     Symbol                                   
>    3.52%          9747  cc1      cc1               [.] bb_is_just_return                   
> #
> 
> and after the fix bb_is_just_return has no recorded samples anymore.
> 
> Thanks,
> Richard.
> 
> 	PR rtl-optimization/109237
> 	* cfgcleanup.cc (bb_is_just_return): Walk insns backwards.

This seems to regress
+FAIL: gcc.dg/guality/pr54200.c   -Os  -DPREVENT_OPTIMIZATION  line 20 z == 3
on x86_64.
This was meant just as a performance improvement, right?
Just with -Os -g0 the assembly difference is:
--- pr54200.s1	2023-03-28 09:45:57.120647323 +0200
+++ pr54200.s2	2023-03-28 09:46:00.423599004 +0200
@@ -19,10 +19,11 @@ foo:
 	cmpl	$1, %esi
 	jne	.L3
 	movl	$2, o(%rip)
-	ret
+	jmp	.L4
 .L3:
 	addl	%esi, %eax
 	addl	%edx, %eax
+.L4:
 	ret
 	.cfi_endproc
 .LFE1:
so 1 byte longer (ret is 1 byte, jmp 2 bytes), but might be also slower.
The difference starts during the pro_and_epilogue pass.

> --- a/gcc/cfgcleanup.cc
> +++ b/gcc/cfgcleanup.cc
> @@ -2608,7 +2608,7 @@ bb_is_just_return (basic_block bb, rtx_insn **ret, rtx_insn **use)
>    if (bb == EXIT_BLOCK_PTR_FOR_FN (cfun))
>      return false;
>  
> -  FOR_BB_INSNS (bb, insn)
> +  FOR_BB_INSNS_REVERSE (bb, insn)
>      if (NONDEBUG_INSN_P (insn))
>        {
>  	rtx pat = PATTERN (insn);
> -- 
> 2.35.3

	Jakub


       reply	other threads:[~2023-03-28  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230322100356.5B99E3857C48@sourceware.org>
2023-03-28  7:49 ` Jakub Jelinek [this message]
2023-03-28  8:40   ` Richard Biener
2023-04-19  7:18 Richard Biener
     [not found] <20230322100405.914ED38582AB@sourceware.org>
2023-03-26 18:01 ` Jeff Law
  -- strict thread matches above, loose matches on Subject: below --
2023-03-22 10:03 Richard Biener

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=ZCKb+Cd8FG8CGugo@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.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).