From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-153387-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30298 invoked by alias); 22 Apr 2009 15:19:20 -0000
Received: (qmail 30278 invoked by uid 22791); 22 Apr 2009 15:19:19 -0000
X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 	tests=AWL,BAYES_00,URI_BLOGSPOT
X-Spam-Check-By: sourceware.org
Received: from web62402.mail.re1.yahoo.com (HELO web62402.mail.re1.yahoo.com) (69.147.75.31)     by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Wed, 22 Apr 2009 15:19:10 +0000
Received: (qmail 15788 invoked by uid 60001); 22 Apr 2009 15:19:07 -0000
Message-ID: <683935.14860.qm@web62402.mail.re1.yahoo.com>
Received: from [164.129.1.42] by web62402.mail.re1.yahoo.com via HTTP; Wed, 22 Apr 2009 08:19:07 PDT
Date: Wed, 22 Apr 2009 20:20:00 -0000
From: Alex Turjan <aturjan@yahoo.com>
Reply-To: aturjan@yahoo.com
Subject: Re: [gSoc] [graphite] general plan for Automatic parallelization in   Graphite
To: gcc@gcc.gnu.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2009-04/txt/msg00581.txt.bz2


Are there any plans to move the partial unrolling phase from
RTL to Tree-SSA?
The move would benefit from better (or easier to implement) Tree-SSA alias analysis. 

Alex
> 
> 
> 
> 
> --- On Wed, 4/22/09, Li Feng <nemokingdom@gmail.com>
> wrote:
> 
> > From: Li Feng <nemokingdom@gmail.com>
> > Subject: [gSoc] [graphite] general plan for Automatic
> parallelization in   Graphite
> > To: "GCC" <gcc@gcc.gnu.org>
> > Cc: "Tobias Grosser"
> <tobi-grosser@web.de>, "Sebastian"
> <sebpop@gmail.com>, "Razya Ladelsky"
> <RAZYA@il.ibm.com>, konrad.trifunovic@gmail.com
> > Date: Wednesday, April 22, 2009, 5:10 PM
> > Hi,
> > 
> > It's nice that the proposal 'Automatic
> > parallelization in Graphite'
> > is accepted. Which means I will be working with great
> > Graphtie
> > developers this summer, and trying to implement the
> project
> > .
> > 
> > I have set up a blog for this project, which will
> mainly
> > about this
> > project: 1. plans 2. what I have done 3. related
> Graphite
> > internals
> > You can subscribe to it if you like:
> > http://summergraphite.blogspot.com/
> > 
> > Here is a general plan for this project, keep you in
> loop,
> > and feel free to comment :)
> > 
> >  1. Mark the innermost loop parallel  [done]
> > 
> >  2. Try to schedule autopar pass after Graphite, and
> enable
> >      code generation if flag_graphite_force_parallel
> is set
> >          - There should be some discussion with Razya
> about
> >            her plan about the autopar part
> >          - But before that, I'll try to schedule
> > autopar first
> > 
> >  3. I may try to write testcases for the loops that
> should
> > be
> >      parallel, from simple to hard, and check
> autopar's
> > code
> >      generation part, make sure this works correctly
> as we
> >      expected.
> >          - The testcases is important. There should be
> some
> >            detailed discussion maybe with Sebastian
> and
> > Konrad.
> >            To see what kind of loop we can/decide to
> > handle.
> >          - Check autopar's code generation with
> >            flag_graphite_force_parallel set with these
> > testcases,
> >            report bugs if it goes wrong.
> > 
> >  4. Try to write code for deciding if a loop can be
> > parallel
> >      with data dependency test under this polyhedral
> model.
> >         - Try to understand the interface of data
> > dependency test
> >         - Write code, if data dependency success, mark
> the
> > loop parallel
> > 
> > Cheers,
> > Li