From: "Bin.Cheng" <amker.cheng@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH BACKPORT]Backport r254778 and test case in r244815 to GCC6
Date: Thu, 01 Feb 2018 12:01:00 -0000 [thread overview]
Message-ID: <CAHFci2_Waa1i2U_MCAuK7adYzhX6-X+zjAZCjroCQQggPPD2Jw@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc2y=++_Mtes00Qo4D69+vnLt5HtFwu-_ww1dLN-G5nydQ@mail.gmail.com>
On Wed, Jan 31, 2018 at 10:55 AM, Richard Biener
<richard.guenther@gmail.com> wrote:
> On Tue, Dec 19, 2017 at 4:36 PM, Bin Cheng <Bin.Cheng@arm.com> wrote:
>> HI,
>> This patch backports r254778 and test case in r244815 to GCC6. Bootstrap and
>> test on x86_64. Is it OK?
>
> Ok.
Retested and applied on GCC6 branch.
Thanks,
bin
>
> Richard.
>
>> Thanks,
>> bin
>>
>> 2017-12-18 Bin Cheng <bin.cheng@arm.com>
>>
>> Backport from mainline
>> 2017-11-15 Bin Cheng <bin.cheng@arm.com>
>>
>> PR tree-optimization/82726
>> PR tree-optimization/70754
>> * tree-predcom.c (order_drefs_by_pos): New function.
>> (combine_chains): Move code setting has_max_use_after to...
>> (try_combine_chains): ...here. New parameter. Sort combined chains
>> according to position information.
>> (tree_predictive_commoning_loop): Update call to above function.
>> (update_pos_for_combined_chains, pcom_stmt_dominates_stmt_p): New.
>>
>> gcc/testsuite
>> 2017-12-18 Bin Cheng <bin.cheng@arm.com>
>>
>> Backport from mainline
>> 2017-11-15 Bin Cheng <bin.cheng@arm.com>
>>
>> PR tree-optimization/82726
>> * gcc.dg/tree-ssa/pr82726.c: New test.
>>
>> Backport from mainline
>> 2017-01-23 Bin Cheng <bin.cheng@arm.com>
>>
>> PR tree-optimization/70754
>> * gfortran.dg/pr70754.f90: New test.
prev parent reply other threads:[~2018-02-01 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 15:36 Bin Cheng
2018-01-31 11:09 ` Richard Biener
2018-02-01 12:01 ` Bin.Cheng [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=CAHFci2_Waa1i2U_MCAuK7adYzhX6-X+zjAZCjroCQQggPPD2Jw@mail.gmail.com \
--to=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).