This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 0/3] [linaro/gcc-4_9-branch] backport fixes to jump-threading
- From: Yvan Roux <yvan dot roux at linaro dot org>
- To: Sebastian Paul Pop <s dot pop at samsung dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Sebastian Pop <sebpop at gmail dot com>, Christophe Lyon <christophe dot lyon at linaro dot org>
- Date: Mon, 31 Aug 2015 18:12:56 +0200
- Subject: Re: [PATCH 0/3] [linaro/gcc-4_9-branch] backport fixes to jump-threading
- Authentication-results: sourceware.org; auth=none
- References: <1441035197-6498-1-git-send-email-s dot pop at samsung dot com> <CAD57uCfqvE_a469OeE_DG+ZQ+adH+mmgcAREpkmgkcAdhXNcgw at mail dot gmail dot com> <00e701d0e407$3aa15520$afe3ff60$ at samsung dot com>
On 31 August 2015 at 18:08, Sebastian Paul Pop <s.pop@samsung.com> wrote:
> I do not intend to back-port the jump-thread patches to the fsf gcc 4.9 branch: the patches I sent are only for the linaro 4.9 branch.
> Yes, please test the patches with your validation suite, and then commit to the linaro branch.
Ok great. Thanks for these backports Sebastian.
Cheers,
Yvan
> Thanks,
> Sebastian
>
> -----Original Message-----
> From: Yvan Roux [mailto:yvan.roux@linaro.org]
> Sent: Monday, August 31, 2015 10:43 AM
> To: Sebastian Pop
> Cc: gcc-patches@gcc.gnu.org; Sebastian Pop; Christophe Lyon
> Subject: Re: [PATCH 0/3] [linaro/gcc-4_9-branch] backport fixes to jump-threading
>
> Hi Sebastian,
>
> On 31 August 2015 at 17:33, Sebastian Pop <s.pop@samsung.com> wrote:
>> Hi,
>>
>> As I was backporting the jump-thread patches to the AOSP gcc 4.9, I found that
>> the linaro branch does not have the following three fixes. Ok to commit to the
>> linaro/gcc-4_9-branch?
>
> Our 4.9 branch is now in maintenance mode, which means that we're only
> backporting bugfixes on it, and synchronizing it with upstream 4.9
> branch. So, if you'll only backport them to AOSP and not FSF gcc 4.9,
> yes it can be beneficial for our branch, but we first have to pass
> them into our validation process.
>
> Cheers,
> Yvan
>
>> Thanks,
>> Sebastian
>>
>> Sebastian Pop (3):
>> backport patch to fix PR65048
>> backport patch to fix PR65177
>> backport fix for PR65735
>>
>> .../gcc/testsuite/gcc.c-torture/compile/pr65735.c | 21 ++++
>> .../testsuite/gcc.dg/tree-ssa/ssa-dom-thread-10.c | 24 ++++
>> .../testsuite/gcc.dg/tree-ssa/ssa-dom-thread-9.c | 50 ++++++++
>> gcc-4.9/gcc/tree-ssa-threadedge.c | 12 +-
>> gcc-4.9/gcc/tree-ssa-threadupdate.c | 133 ++++++++++++++++-----
>> 5 files changed, 202 insertions(+), 38 deletions(-)
>> create mode 100644 gcc-4.9/gcc/testsuite/gcc.c-torture/compile/pr65735.c
>> create mode 100644 gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-10.c
>> create mode 100644 gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-9.c
>>
>> --
>> 2.1.0.243.g30d45f7
>>
>