public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Bin Cheng <Bin.Cheng@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH PR71347][Partial revert r235513]Compute cost for all uses in group
Date: Mon, 13 Jun 2016 10:10:00 -0000	[thread overview]
Message-ID: <CAFiYyc20TcXbYNnhs1MvaTsonhv817Pa4mSbDK-oRHDHS4aTHQ@mail.gmail.com> (raw)
In-Reply-To: <DB5PR08MB1144BCACC3F137372BAC7A63E7530@DB5PR08MB1144.eurprd08.prod.outlook.com>

On Mon, Jun 13, 2016 at 11:57 AM, Bin Cheng <Bin.Cheng@arm.com> wrote:
> Hi,
> This patch partially reverts part of r235513 to fix PR71347, the original patch is to improve compilation time for a small amount.  Root cause as analyzed in bugzilla PR is that we can't skip computing cost for sub iv_use if it has different position to the first use in group.  The patch also includes a new test.
>
> Bootstrap and test on x86_64.  Is it OK?

Ok.

Richard.

> Thanks,
> bin
>
> 2016-05-31  Bin Cheng  <bin.cheng@arm.com>
>
>         PR tree-optimization/71347
>         * tree-ssa-loop-ivopts.c (determine_group_iv_cost_address): Compute
>         cost for all uses in group.
>
> gcc/testsuite/ChangeLog
> 2016-05-31  Bin Cheng  <bin.cheng@arm.com>
>
>         PR tree-optimization/71347
>         * gcc.dg/tree-ssa/pr71347.c: New test.

  reply	other threads:[~2016-06-13 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  9:57 Bin Cheng
2016-06-13 10:10 ` Richard Biener [this message]
2016-06-18  8:59 ` Andreas Schwab
2016-06-20  8:18   ` Christophe Lyon
2016-06-20  8:20     ` Bin.Cheng
2016-06-20  9:11       ` Bin.Cheng
2016-06-20  9:19         ` Andreas Schwab

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=CAFiYyc20TcXbYNnhs1MvaTsonhv817Pa4mSbDK-oRHDHS4aTHQ@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=Bin.Cheng@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.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).