public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix ICE during strstr gimple folding (PR middle-end/81207)
Date: Tue, 27 Jun 2017 07:11:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1706270910080.23185@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20170627054632.GM2123@tucnak>

On Tue, 27 Jun 2017, Jakub Jelinek wrote:

> Hi!
> 
> replace_call_with_call_and_fold has code to copy over vdef/vuse from the
> old call to the new one, so that we don't have to update virtual ssa,
> but it is conditioned on gimple_vdef being non-NULL and SSA_NAME.
> If we have a pure function, gimple_vdef is NULL, yet we still want to copy
> over the vuse.
> 
> Bootstrapped/regtested on x86_64-linux (i686-linux fails to bootstrap
> with/without this patch), ok for trunk?

Ok with ...

> 2017-06-27  Jakub Jelinek  <jakub@redhat.com>
> 
> 	PR middle-end/81207
> 	* gimple-fold.c (replace_call_with_call_and_fold): Handle
> 	gimple_vuse copying separately from gimple_vdef copying.
> 
> 	* gcc.c-torture/compile/pr81207.c: New test.
> 
> --- gcc/gimple-fold.c.jj	2017-06-19 08:28:11.000000000 +0200
> +++ gcc/gimple-fold.c	2017-06-26 17:09:34.735420583 +0200
> @@ -607,9 +607,11 @@ replace_call_with_call_and_fold (gimple_
>        && TREE_CODE (gimple_vdef (stmt)) == SSA_NAME)
>      {
>        gimple_set_vdef (repl, gimple_vdef (stmt));
> -      gimple_set_vuse (repl, gimple_vuse (stmt));
>        SSA_NAME_DEF_STMT (gimple_vdef (repl)) = repl;
>      }
> +  if (gimple_vuse (stmt)
> +      && TREE_CODE (gimple_vuse (stmt)) == SSA_NAME)

... the SSA_NAME check removed.  It's done above because we access
SSA_NAME_DEF_STMT, here it isn't necessary.

> +    gimple_set_vuse (repl, gimple_vuse (stmt));
>    gsi_replace (gsi, repl, false);
>    fold_stmt (gsi);
>  }
> --- gcc/testsuite/gcc.c-torture/compile/pr81207.c.jj	2017-06-26 17:21:38.765918367 +0200
> +++ gcc/testsuite/gcc.c-torture/compile/pr81207.c	2017-06-26 17:27:15.222966965 +0200
> @@ -0,0 +1,13 @@
> +/* PR middle-end/81207 */
> +
> +static const char *b[2] = { "'", "" };
> +
> +int
> +foo (const char *d)
> +{
> +  int e;
> +  for (e = 0; b[e]; e++)
> +    if (__builtin_strstr (d, b[e]))
> +      return 1;
> +  return 0;
> +}
> 
> 	Jakub
> 
> 

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

      reply	other threads:[~2017-06-27  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27  5:47 Jakub Jelinek
2017-06-27  7:11 ` Richard Biener [this message]

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.20.1706270910080.23185@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).