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: Jeff Law <law@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][RFC] Fix PR61473, inline small memcpy/memmove during tree opts
Date: Fri, 11 Jul 2014 08:03:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1407111000040.5753@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20140710151259.GL31640@tucnak.redhat.com>

On Thu, 10 Jul 2014, Jakub Jelinek wrote:

> On Thu, Jul 10, 2014 at 04:30:13PM +0200, Richard Biener wrote:
> > Compromise "hack" below.  It simply avoids the transform for
> > sources that c_strlen can compute a length of.  That "fixes" all
> > strlenopt testcase apart from strlenopt-8.c which does
> > memcpy (, flag ? "a" : "b"); which then still folds
> > during gimplification.  I have XFAILed that.
> > 
> > I've tried to comb my way through strlenopt but failed to quickly
> > add support for generic stores (it has very rough support for
> > char stores, see also PR61773).
> > 
> > Does the below look ok?
> 
> I can look at the tree-ssa-strlen.c stuff and removing the !c_strlen
> hack incrementally.

Ok, I'll bootstrap/test the patch then and will commit if there are
no issues left.

Thanks,
Richard.

  reply	other threads:[~2014-07-11  8:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 10:15 Richard Biener
2014-06-12 20:32 ` Jeff Law
2014-06-27 11:52   ` Richard Biener
2014-06-27 11:57     ` Jakub Jelinek
2014-06-27 12:01       ` Richard Biener
2014-07-10 14:33         ` Richard Biener
2014-07-10 15:13           ` Jakub Jelinek
2014-07-11  8:03             ` Richard Biener [this message]
2014-07-11 13:39               ` Richard Biener
2014-07-11 13:42                 ` Jakub Jelinek
2014-07-14  7:54                   ` Richard Biener
2014-07-14 11:12                     ` Richard Biener
2014-06-27 15:44       ` 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=alpine.LSU.2.11.1407111000040.5753@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=law@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).