install.texi: Remove mentions of cloog and ppl.
* doc/install.texi: Remove mentions of cloog and ppl. * doc/invoke.texi: Likewise From-SVN: r218348
This commit is contained in:
parent
c05eeebc17
commit
8495b8f693
@ -1,3 +1,8 @@
|
||||
2014-12-04 Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
|
||||
|
||||
* doc/install.texi: Remove mentions of cloog and ppl.
|
||||
* doc/invoke.texi: Likewise
|
||||
|
||||
2014-12-04 Jakub Jelinek <jakub@redhat.com>
|
||||
|
||||
PR c++/56493
|
||||
|
@ -1719,21 +1719,13 @@ a cross compiler, they will not be used to configure target libraries.
|
||||
@item --with-isl=@var{pathname}
|
||||
@itemx --with-isl-include=@var{pathname}
|
||||
@itemx --with-isl-lib=@var{pathname}
|
||||
@itemx --with-cloog=@var{pathname}
|
||||
@itemx --with-cloog-include=@var{pathname}
|
||||
@itemx --with-cloog-lib=@var{pathname}
|
||||
If you do not have ISL and the CLooG
|
||||
libraries installed in a standard location and you want to build GCC,
|
||||
you can explicitly specify the directory where they are installed
|
||||
(@samp{--with-isl=@/@var{islinstalldir}},
|
||||
@samp{--with-cloog=@/@var{clooginstalldir}}). The
|
||||
If you do not have the ISL library installed in a standard location and you
|
||||
want to build GCC, you can explicitly specify the directory where it is
|
||||
installed (@samp{--with-isl=@/@var{islinstalldir}}). The
|
||||
@option{--with-isl=@/@var{islinstalldir}} option is shorthand for
|
||||
@option{--with-isl-lib=@/@var{islinstalldir}/lib} and
|
||||
@option{--with-isl-include=@/@var{islinstalldir}/include}. Likewise the
|
||||
@option{--with-cloog=@/@var{clooginstalldir}} option is shorthand for
|
||||
@option{--with-cloog-lib=@/@var{clooginstalldir}/lib} and
|
||||
@option{--with-cloog-include=@/@var{clooginstalldir}/include}. If these
|
||||
shorthand assumptions are not correct, you can use the explicit
|
||||
@option{--with-isl-include=@/@var{islinstalldir}/include}. If this
|
||||
shorthand assumption is not correct, you can use the explicit
|
||||
include and lib options directly.
|
||||
|
||||
These flags are applicable to the host platform only. When building
|
||||
|
@ -8245,8 +8245,8 @@ at @option{-O} and higher.
|
||||
@opindex ftree-loop-linear
|
||||
Perform loop interchange transformations on tree. Same as
|
||||
@option{-floop-interchange}. To use this code transformation, GCC has
|
||||
to be configured with @option{--with-ppl} and @option{--with-cloog} to
|
||||
enable the Graphite loop transformation infrastructure.
|
||||
to be configured with @option{--with-isl} to enable the Graphite loop
|
||||
transformation infrastructure.
|
||||
|
||||
@item -floop-interchange
|
||||
@opindex floop-interchange
|
||||
@ -8274,8 +8274,8 @@ contiguously by column, and the original loop iterates over rows,
|
||||
potentially creating at each access a cache miss. This optimization
|
||||
applies to all the languages supported by GCC and is not limited to
|
||||
Fortran. To use this code transformation, GCC has to be configured
|
||||
with @option{--with-ppl} and @option{--with-cloog} to enable the
|
||||
Graphite loop transformation infrastructure.
|
||||
with @option{--with-isl} to enable the Graphite loop transformation
|
||||
infrastructure.
|
||||
|
||||
@item -floop-strip-mine
|
||||
@opindex floop-strip-mine
|
||||
@ -8300,8 +8300,8 @@ ENDDO
|
||||
@end smallexample
|
||||
This optimization applies to all the languages supported by GCC and is
|
||||
not limited to Fortran. To use this code transformation, GCC has to
|
||||
be configured with @option{--with-ppl} and @option{--with-cloog} to
|
||||
enable the Graphite loop transformation infrastructure.
|
||||
be configured with @option{--with-isl} to enable the Graphite loop
|
||||
transformation infrastructure.
|
||||
|
||||
@item -floop-block
|
||||
@opindex floop-block
|
||||
@ -8333,9 +8333,8 @@ which can be beneficial when @code{M} is larger than the caches,
|
||||
because the innermost loop iterates over a smaller amount of data
|
||||
which can be kept in the caches. This optimization applies to all the
|
||||
languages supported by GCC and is not limited to Fortran. To use this
|
||||
code transformation, GCC has to be configured with @option{--with-ppl}
|
||||
and @option{--with-cloog} to enable the Graphite loop transformation
|
||||
infrastructure.
|
||||
code transformation, GCC has to be configured with @option{--with-isl}
|
||||
to enable the Graphite loop transformation infrastructure.
|
||||
|
||||
@item -fgraphite-identity
|
||||
@opindex fgraphite-identity
|
||||
@ -8343,7 +8342,7 @@ Enable the identity transformation for graphite. For every SCoP we generate
|
||||
the polyhedral representation and transform it back to gimple. Using
|
||||
@option{-fgraphite-identity} we can check the costs or benefits of the
|
||||
GIMPLE -> GRAPHITE -> GIMPLE transformation. Some minimal optimizations
|
||||
are also performed by the code generator CLooG, like index splitting and
|
||||
are also performed by the code generator ISL, like index splitting and
|
||||
dead code elimination in loops.
|
||||
|
||||
@item -floop-nest-optimize
|
||||
|
Loading…
Reference in New Issue
Block a user