public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR79547
Date: Fri, 17 Feb 2017 10:52:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.20.1702171131030.2176@stedding.saclay.inria.fr> (raw)
In-Reply-To: <alpine.LSU.2.20.1702171042390.8538@zhemvz.fhfr.qr>

On Fri, 17 Feb 2017, Richard Biener wrote:

> On Thu, 16 Feb 2017, Richard Biener wrote:
>
>>
>> I am testing the following patch for PR79547.  Those builtins do not
>> return anything that can be used to re-construct the pointer(s) passed
>> to them.
>>
>> Queued for GCC 8.
>
> Actually we need calluse constraints.  Thus adjusted as follows.
>
> Richard.
>
> 2017-02-17  Richard Biener  <rguenther@suse.de>
>
> 	PR tree-optimization/79547
> 	* tree-ssa-structalias.c (find_func_aliases_for_builtin_call):
> 	Handle strlen, strcmp, strncmp, strcasecmp, strncasecmp, memcmp,
> 	bcmp, strspn, strcspn, __builtin_object_size and __builtin_constant_p
> 	without any constraints.

We have EAF_NOESCAPE that we are using for non-builtins, though it 
probably gets little use there. Would it make sense to use it here as 
well, or would that be pointless?

-- 
Marc Glisse

  reply	other threads:[~2017-02-17 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 12:47 Richard Biener
2017-02-17  9:45 ` Richard Biener
2017-02-17 10:52   ` Marc Glisse [this message]
2017-02-17 11:32     ` Richard Biener
2017-04-21 13:08   ` 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=alpine.DEB.2.20.1702171131030.2176@stedding.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --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).