public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Handle CONSTRUCTOR in operand_equal_p
Date: Thu, 22 Oct 2015 07:39:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1510220929370.16509@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20151021190529.GB92763@kam.mff.cuni.cz>

On Wed, 21 Oct 2015, Jan Hubicka wrote:

> Hi,
> this is updated patch I am going to commit.  As discussed, we also need to match
> non-empty CONSTRUCTOR of vectors, but those should never be having CONSTANT flags
> set, so they need care in the other path trhough operand_equal_p, so I will post
> separate patch for that.
> 
> I updated the comment per Richard's comment and added a testcase.  Vuriously
> enoug we fold "val? (struct a){} : (struct a){}" only in PRE (tailmerging).
> W/o the patch even .optimized dump has the test and we fold it away only after
> lowering to RTL:
> ret (int val)
> {
>   struct a D.1764;
> 
>   <bb 2>:
>   if (val_2(D) != 0)
>     goto <bb 3>;
>   else
>     goto <bb 4>;
> 
>   <bb 3>:
>   D.1764 = {};
>   goto <bb 5>;
> 
>   <bb 4>:
>   D.1764 = {};
> 
>   <bb 5>:
>   return D.1764;
> 
> }
> 
> ret:
> .LFB0:
>         .cfi_startproc
>         xorl    %eax, %eax
>         ret
>         .cfi_endproc
> 
> With the patch we get:
> 
> ret (int val)
> {
>   struct a D.1764;
> 
>   <bb 2>:
>   D.1764 = {};
>   return D.1764;
> 
> }

But only via GENERIC folding I suppose.  Yes, we don't value-number
aggregates and generally PRE (and DOM via excessive jump-threading)
is the only pass that remotely handles this kind of situation.

code hoisting/sinking would maybe catch this but as this involves
memory I'm not sure the implementation ontop of PRE that is stuck
in some PR would catch it.

Richard.

> Honza
> 
> 	* fold-const.c (operand_equal_p): Add code matching empty
> 	constructors.
> 	* gcc.dg/tree-ssa/operand-equal-1.c: Verify that empty constructors
> 	are matched.
> 
> Index: fold-const.c
> ===================================================================
> --- fold-const.c	(revision 229133)
> +++ fold-const.c	(working copy)
> @@ -2892,6 +2892,11 @@ operand_equal_p (const_tree arg0, const_
>  	return operand_equal_p (TREE_OPERAND (arg0, 0), TREE_OPERAND (arg1, 0),
>  				flags | OEP_ADDRESS_OF
>  				| OEP_CONSTANT_ADDRESS_OF);
> +      case CONSTRUCTOR:
> +	/* In GIMPLE empty constructors are allowed in initializers of
> +	   aggregates.  */
> +	return (!vec_safe_length (CONSTRUCTOR_ELTS (arg0))
> +		&& !vec_safe_length (CONSTRUCTOR_ELTS (arg1)));
>        default:
>  	break;
>        }
> Index: testsuite/gcc.dg/tree-ssa/operand-equal-1.c
> ===================================================================
> --- testsuite/gcc.dg/tree-ssa/operand-equal-1.c	(revision 0)
> +++ testsuite/gcc.dg/tree-ssa/operand-equal-1.c	(revision 0)
> @@ -0,0 +1,8 @@
> +/* { dg-do compile } */
> +/* { dg-options "-O2 -fdump-tree-pre" } */
> +struct a {int a,b;};
> +struct a ret(int val)
> +{
> +   return val? (struct a){} : (struct a){};
> +}
> +/* { dg-final { scan-tree-dump-not "if " "pre"} } */
> 
> 

-- 
Richard Biener <rguenther@suse.de>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

  reply	other threads:[~2015-10-22  7:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 16:27 Jan Hubicka
2015-10-14 17:26 ` Jeff Law
2015-10-14 17:35   ` Jan Hubicka
2015-10-14 18:42 ` Richard Biener
2015-10-14 23:55   ` Jan Hubicka
2015-10-15  6:57     ` Richard Biener
2015-10-21 19:10       ` Jan Hubicka
2015-10-22  7:39         ` Richard Biener [this message]
2015-10-23  5:43           ` Jan Hubicka

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=alpine.LSU.2.11.1510220929370.16509@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    /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).