This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Fw: [patch][wwwdocs] 4.5/changes.html: Add autopar changes
gcc-graphite@googlegroups.com wrote on 05/11/2009 02:41:18:
> Gerald Pfeifer <gerald@pfeifer.com>
> Sent by: gcc-graphite@googlegroups.com
>
> 05/11/2009 02:41
>
> To
>
> Razya Ladelsky/Haifa/IBM@IBMIL
>
> cc
>
> gcc-patches@gcc.gnu.org, gcc-graphite@googlegroups.com
>
> Subject
>
> Re: Fw: [patch][wwwdocs] 4.5/changes.html: Add autopar changes
>
>
> Hi Razya,
>
> On Tue, 3 Nov 2009, Razya Ladelsky wrote:
> > I documented the changes in autopar for GCC4.5.
> > Ok to commit?
>
> this looks good, thanks for taking the time to write it up. I just
> have one question for my own understanding (which may or may not be
> relevant to consider for the change):
>
> > + <li>The automatic parallelization pass was enhanced to support
> > + parallelization of outer loops.</li>
> > +
> > + <li>Automatic parallelization can be enabled as part of Graphite.
> > + Both <code>-ftree-parallelize-loops=*</code> and
> > + <code>-floop-parallelize-all</code>need to be turned on.</li>
>
> How does automatic parallelization relate to Graphite? My understanding
> is that we have automatic parallelization both without Graphite and now
> with Graphite, too, and that -ftree-parallelize-loops= is the general
> option and that -floop-parallelize-all comes from Graphite.
Yes, exactly.
> If that
> is the case, perhaps something like "In addition to
-ftree-parallelize-loops=,
> specify -floop-parallelize-all to enable the Graphite-based
optimization"
> or something like that?
Yes, if that seems clearer, I will adopt it:
+ <li>Automatic parallelization can be enabled as part of Graphite.
+ In addition to <code>-ftree-parallelize-loops=</code>, specify
+ <code>-floop-parallelize-all</code> to enable the Graphite-based
+ optimization.</li>
+
Thanks a lot,
Razya
>
> (Otherwise there is a blank missing before "need".)
>
> Gerald