This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Autoparallelization
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
- Cc: gcc-patches at gcc dot gnu dot org, sebastian dot pop at cri dot ensmp dot fr
- Date: Tue, 03 Oct 2006 09:14:01 -0400
- Subject: Re: Autoparallelization
- References: <20060927210927.GA30121@atrey.karlin.mff.cuni.cz>
[ Apologies for the duplicate. The original message had the wrong
return address for gcc-patches. ]
Zdenek Dvorak wrote on 09/27/06 17:09:
> I have commited the following patch to parloop branch. It implements
> automatic parallelization for simple loops; at the moment, code
> generation only creates static schedule into fixed number of threads
> (specified at compile time). This should more or less be the version
> I would like to get merged to 4.3 (I probably won't have time to
> implement more features in following few weeks).
>
I have started going through the code. One question regarding the
approach: Why didn't you folks generate OMP_PARALLEL/OMP_FOR? The
intent was for auto-parallelization passes to target the OMP IL, not
libgomp. If there is anything that needs to be fixed in the OMP code,
this is our chance to do it.
We have this impedance with OMP and the SSA form, but as a design goal,
I would really want to target the generation of OMP instructions. It
will allow us to hide the mechanics of parallel code generation better.