public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Pop <sebpop@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: rguenther@suse.de,	gcc-graphite@googlegroups.com,
	Sebastian Pop <sebpop@gmail.com>
Subject: [PATCH 00/10] Make -floop-interchange catch almost all testcases of -ftree-loop-linear
Date: Sat, 15 Jan 2011 09:09:00 -0000	[thread overview]
Message-ID: <1295082315-32242-1-git-send-email-sebpop@gmail.com> (raw)

Hi Richi,

Here is the first part of the patch to remove the lambda framework.
These patches un-xfail most of the transforms that we wanted to see
with -floop-interchange and that were part of the testsuite of
-ftree-loop-linear:

gcc.dg/graphite/block-0.c
gcc.dg/graphite/block-1.c
gcc.dg/graphite/block-4.c
gcc.dg/graphite/block-7.c
gcc.dg/graphite/block-8.c
gcc.dg/graphite/interchange-1.c
gcc.dg/graphite/interchange-11.c
gcc.dg/graphite/interchange-12.c
gcc.dg/graphite/interchange-13.c
gcc.dg/graphite/interchange-14.c
gcc.dg/graphite/interchange-15.c
gcc.dg/graphite/interchange-8.c
gcc.dg/graphite/interchange-mvt.c

The only xfails remaining to be fixed before removing the lambda
framework are: 
- interchange-2.c: some problem linked to the scop detection
- interchange-3.f90: data dependence analysis does not validate the interchange.
I will continue my investigation on these two xfails.

With the patches, the Graphite testsuite has the following XFAILs:

block-4.c:59:/* { dg-final { scan-tree-dump-times "will be loop blocked" 1 "graphite" { xfail *-*-* } } } */
interchange-2.c:55:/* { dg-final { scan-tree-dump-times "will be interchanged" 1 "graphite" { xfail *-*-* } } } */ 
pr35356-3.c:39:/* { dg-final { scan-tree-dump-times "loop_1" 0 "graphite" { xfail *-*-* } } } */
pr37485.c:31:/* { dg-final { scan-tree-dump-times "Loop blocked" 1 "graphite" { xfail *-*-* }} } */

block-1.f90:11:! { dg-final { scan-tree-dump-times "will be loop blocked" 1 "graphite" { xfail *-*-* } } }
block-2.f:20:! { dg-final { scan-tree-dump-times "will be loop blocked" 2 "graphite" { xfail *-*-* } } }
block-3.f90:15:! { dg-final { scan-tree-dump-times "number of SCoPs: 1" 1 "graphite" { xfail *-*-* } } }
block-3.f90:16:! { dg-final { scan-tree-dump-times "will be loop blocked" 1 "graphite" { xfail *-*-* } } }
block-4.f90:18:! { dg-final { scan-tree-dump-times "number of SCoPs: 1" 1 "graphite" { xfail *-*-* } } }
block-4.f90:19:! { dg-final { scan-tree-dump-times "will be loop blocked" 1 "graphite" { xfail *-*-* } } }
interchange-1.f:44:! { dg-final { scan-tree-dump-times "will be interchanged" 1 "graphite" { xfail *-*-* } } }
interchange-3.f90:27:! { dg-final { scan-tree-dump-times "will be interchanged" 1 "graphite" { xfail *-*-* } } }
pr14741.f90:27:! { dg-final { scan-tree-dump-times "number of SCoPs: 1" 1 "graphite" { xfail *-*-* } } }
pr14741.f90:28:! { dg-final { scan-tree-dump-times "will be loop blocked" 1 "graphite" { xfail *-*-* } } }
scop-1.f:12:! { dg-final { scan-tree-dump-times "number of SCoPs: 1" 1 "graphite" { xfail *-*-* } } } 

I'm committing these patches to the graphite branch for regstrap and
SPEC testing.

Sebastian Pop (10):
  Add debug_gmp_value.
  Print the data dependence polyhedron in the PPL format.
  Test the profitability of interchange on the perfect nest.
  Fix pbb_remove_duplicate_pdrs.
  speedup compilation
  Correct the precedence relation.
  Use PIP to determine the integer feasibility of a constraint system.
  Minimize the number of expensive calls to ppl_powerset_is_empty.
  Expect at least the version 0.11 of PPL.
  Remove the temporary array for reductions written to memory.

 ChangeLog.graphite                              |    5 +
 configure                                       |    6 +-
 configure.ac                                    |    4 +-
 gcc/ChangeLog.graphite                          |   96 ++++++++++
 gcc/doc/install.texi                            |    2 +-
 gcc/graphite-dependences.c                      |  226 +++++++++--------------
 gcc/graphite-interchange.c                      |   16 +-
 gcc/graphite-poly.c                             |   13 +-
 gcc/graphite-ppl.c                              |   76 ++++++++
 gcc/graphite-ppl.h                              |    3 +
 gcc/graphite-sese-to-poly.c                     |   43 ++++-
 gcc/testsuite/gcc.dg/graphite/block-0.c         |    3 +-
 gcc/testsuite/gcc.dg/graphite/block-1.c         |    5 +-
 gcc/testsuite/gcc.dg/graphite/block-4.c         |    2 +
 gcc/testsuite/gcc.dg/graphite/block-7.c         |    3 +-
 gcc/testsuite/gcc.dg/graphite/block-8.c         |   58 ++++++
 gcc/testsuite/gcc.dg/graphite/interchange-1.c   |    4 +-
 gcc/testsuite/gcc.dg/graphite/interchange-11.c  |    3 +-
 gcc/testsuite/gcc.dg/graphite/interchange-12.c  |    3 +-
 gcc/testsuite/gcc.dg/graphite/interchange-13.c  |   54 ++++++
 gcc/testsuite/gcc.dg/graphite/interchange-14.c  |   58 ++++++
 gcc/testsuite/gcc.dg/graphite/interchange-15.c  |   53 ++++++
 gcc/testsuite/gcc.dg/graphite/interchange-8.c   |    5 +-
 gcc/testsuite/gcc.dg/graphite/interchange-mvt.c |    3 +-
 gcc/tree-data-ref.c                             |    4 +-
 25 files changed, 573 insertions(+), 175 deletions(-)
 create mode 100644 gcc/testsuite/gcc.dg/graphite/block-8.c
 create mode 100644 gcc/testsuite/gcc.dg/graphite/interchange-13.c
 create mode 100644 gcc/testsuite/gcc.dg/graphite/interchange-14.c
 create mode 100644 gcc/testsuite/gcc.dg/graphite/interchange-15.c

             reply	other threads:[~2011-01-15  9:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  9:09 Sebastian Pop [this message]
2011-01-15  9:09 ` [PATCH 02/10] Print the data dependence polyhedron in the PPL format Sebastian Pop
2011-01-15  9:09 ` [PATCH 01/10] Add debug_gmp_value Sebastian Pop
2011-01-15  9:09 ` [PATCH 09/10] Expect at least the version 0.11 of PPL Sebastian Pop
2011-01-15  9:09 ` [PATCH 06/10] Correct the precedence relation Sebastian Pop
2011-01-15  9:09 ` [PATCH 04/10] Fix pbb_remove_duplicate_pdrs Sebastian Pop
2011-01-15  9:09 ` [PATCH 08/10] Minimize the number of expensive calls to ppl_powerset_is_empty Sebastian Pop
2011-01-15  9:09 ` [PATCH 05/10] speedup compilation Sebastian Pop
2011-01-15  9:28 ` [PATCH 10/10] Remove the temporary array for reductions written to memory Sebastian Pop
     [not found]   ` <AANLkTikHnNc5jznpHA51TySErrZ=7tiMYBFowcxLqk1a@mail.gmail.com>
2011-01-19 19:59     ` Sebastian Pop
2011-01-20  0:20       ` [PATCH 0/3] Fix 3 SPEC compile fails Sebastian Pop
2011-01-20  0:29       ` [PATCH 3/3] Only copy PBB_DOMAIN when it is initialized Sebastian Pop
2011-01-20  2:26       ` [PATCH 1/3] Move rewrite_commutative_reductions_out_of_ssa before find_scop_parameters Sebastian Pop
2011-01-20  4:08       ` [PATCH 2/3] Pass to dr_analyze_indices the analysis loop for subscripts Sebastian Pop
2011-01-15 10:09 ` [PATCH 03/10] Test the profitability of interchange on the perfect nest Sebastian Pop
2011-01-15 10:54 ` [PATCH 07/10] Use PIP to determine the integer feasibility of a constraint system Sebastian Pop
2011-01-15 18:54   ` Sven Verdoolaege
2011-01-15 22:08     ` Sebastian Pop
2011-01-15 22:27       ` Sven Verdoolaege
2011-01-17 10:43         ` [PATCH] Pass 0 as the number of parameters to PIP when testing for integer feasibility Sebastian Pop
2011-01-17  6:31 ` [PATCH 00/10] Make -floop-interchange catch almost all testcases of -ftree-loop-linear 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=1295082315-32242-1-git-send-email-sebpop@gmail.com \
    --to=sebpop@gmail.com \
    --cc=gcc-graphite@googlegroups.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).