This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Automatic Parallelization & Graphite - future plans
- From: Joern Rennecke <amylaar at spamcop dot net>
- To: Razya Ladelsky <RAZYA at il dot ibm dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 18 Mar 2009 09:49:20 -0400
- Subject: Re: Automatic Parallelization & Graphite - future plans
I'd like to explore distributing threads across a heterogenous NUMA
architecture. I.e. input/output data would have to be transferred
explicitly, and the compiler would have to have more than one backend.
Would such work be appropriate for an existing branch, or should I better
work on my own branch for that?
And do the current autoparallelization algorithms find or propagate sufficent
alias information ((not always, obviously, but at least sometimes) to
determine
if offloading a job to another processor with separate memories is safe and
likely to be worthwhile?