From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Sebastian Pop <sebpop@gmail.com>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de,
gcc-graphite@googlegroups.com
Subject: Re: [PATCH 0/5] Remove the LAMBDA framework
Date: Tue, 18 Jan 2011 14:46:00 -0000 [thread overview]
Message-ID: <20110118143444.GA3407@bromo.med.uc.edu> (raw)
In-Reply-To: <1295329083-27160-1-git-send-email-sebpop@gmail.com>
On Mon, Jan 17, 2011 at 11:37:58PM -0600, Sebastian Pop wrote:
> Hi Richi,
>
> Here is the second part of the patches that completely remove the
> LAMBDA framework and fixes at least the following PRs from my todo
> list: 29832, 43567, 43657, 46168.
>
> The patches remove the XFAIL from the loop kernel interchange-3.f90
> that represents the swim kernel. The ltrans-* testcases are now in
> the graphite testsuite and all passing except interchange-2.c that has
> a SCoP detection problem: a loop with two exits is not yet handled in
> the Graphite framework. This will be fixed later.
>
> I will commit these patches to the graphite branch for further tests
> sometime tomorrow if there are no further comments.
Sebastian,
Are there duplications in the fifth patch?
[PATCH 5/5] Remove the lambda framework and make -ftree-loop-linear an alias of -floop-interchange.
When I apply the 10 patches from the series in http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01036.html,
the follow patch from http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01117.html and these five patches,
the one from http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01186.html gives...
patching file gcc/lambda-mat.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/lambda-mat.c.rej
patching file gcc/lambda-trans.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/lambda-trans.c.rej
patching file gcc/lambda.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file gcc/lambda.h.rej
Thanks in advance for any clarifications.
Jack
>
> Thanks,
> Sebastian
>
> Sebastian Pop (5):
> Relax the definition of same_pdr_p.
> Remove duplicate close phi nodes in the canonical close phi
> representation.
> Allow several reductions in a reduction PBB.
> Do not create the temporary array for reductions into VAR_DECLs.
> Remove the lambda framework and make -ftree-loop-linear an alias of
> -floop-interchange.
>
> ChangeLog.graphite | 4 +
> MAINTAINERS | 1 -
> gcc/ChangeLog.graphite | 86 +
> gcc/Makefile.in | 17 +-
> gcc/graphite-dependences.c | 10 +-
> gcc/graphite-poly.h | 3 +-
> gcc/graphite-scop-detection.c | 69 +-
> gcc/graphite-sese-to-poly.c | 7 +-
> gcc/lambda-code.c | 2855 --------------------
> gcc/lambda-mat.c | 607 -----
> gcc/lambda-trans.c | 80 -
> gcc/lambda.h | 524 ----
> gcc/lto-symtab.c | 1 -
> gcc/passes.c | 1 -
> .../gfortran.dg/graphite/interchange-3.f90 | 2 +-
> gcc/tree-data-ref.c | 174 ++
> gcc/tree-data-ref.h | 143 +-
> gcc/tree-loop-linear.c | 423 ---
> gcc/tree-parloops.c | 119 +
> gcc/tree-pass.h | 3 +-
> gcc/tree-ssa-loop.c | 44 +-
> 21 files changed, 603 insertions(+), 4570 deletions(-)
> delete mode 100644 gcc/lambda-code.c
> delete mode 100644 gcc/lambda-mat.c
> delete mode 100644 gcc/lambda-trans.c
> delete mode 100644 gcc/lambda.h
> delete mode 100644 gcc/tree-loop-linear.c
next prev parent reply other threads:[~2011-01-18 14:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 5:38 Sebastian Pop
2011-01-18 5:38 ` [PATCH 1/5] Relax the definition of same_pdr_p Sebastian Pop
2011-01-18 5:40 ` [PATCH 3/5] Allow several reductions in a reduction PBB Sebastian Pop
2011-01-18 7:45 ` [PATCH 2/5] Remove duplicate close phi nodes in the canonical close phi representation Sebastian Pop
2011-01-18 8:45 ` [PATCH 4/5] Do not create the temporary array for reductions into VAR_DECLs Sebastian Pop
2011-01-18 10:50 ` Richard Guenther
2011-01-18 9:03 ` [PATCH 5/5] Remove the lambda framework and make -ftree-loop-linear an alias of -floop-interchange Sebastian Pop
2011-01-18 10:52 ` Richard Guenther
2011-01-18 16:48 ` Sebastian Pop
2011-01-25 23:39 ` Joseph S. Myers
2011-01-27 10:38 ` Jay Foad
2011-01-28 18:12 ` [PATCH] Use HOST_WIDE_INTs in gcd and least_common_multiple Sebastian Pop
2011-01-28 19:01 ` Joseph S. Myers
2011-01-28 22:18 ` Sebastian Pop
2011-01-31 12:35 ` Richard Guenther
2011-01-31 22:37 ` Joseph S. Myers
2011-02-04 4:08 ` Sebastian Pop
2011-02-04 23:13 ` Richard Guenther
2011-07-29 8:27 ` Sebastian Pop
2011-07-30 7:22 ` Richard Henderson
2011-01-31 14:36 ` Jay Foad
2011-01-31 14:43 ` Joseph S. Myers
2011-01-31 14:53 ` Jay Foad
2011-01-26 12:22 ` [PATCH 5/5] Remove the lambda framework and make -ftree-loop-linear an alias of -floop-interchange Eric Botcazou
2011-01-26 13:32 ` Richard Guenther
2011-01-26 15:59 ` Eric Botcazou
2011-01-26 22:43 ` Eric Botcazou
2011-01-25 23:28 ` Joseph S. Myers
2011-01-28 22:42 ` [PATCH] Use Alias in common.opt to " Sebastian Pop
2011-01-29 9:58 ` Jack Howarth
2011-01-29 10:54 ` Sebastian Pop
2011-01-31 12:41 ` Richard Guenther
2011-01-18 14:46 ` Jack Howarth [this message]
2011-01-18 16:56 ` [PATCH 0/5] Remove the LAMBDA framework Sebastian Pop
2011-01-18 17:08 ` Sebastian Pop
2011-01-18 18:20 ` Jack Howarth
2011-01-18 18:54 ` Sebastian Pop
2011-01-18 19:58 ` Jack Howarth
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=20110118143444.GA3407@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gcc-graphite@googlegroups.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=sebpop@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).