Hi Sebastian, On 31 August 2015 at 17:33, Sebastian Pop <s....@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 >
