Thanks all for supporting the idea of enabling graphite.
We would collect compile-time, performance, code-size data and let you
know. We are very positive that the compile time would have improved
on an average,
because of new scop detection algorithm.
With the new set of patches graphite does not
On Fri, 13 Nov 2015, VandeVondele Joost wrote:
> I'm all in favour of requiring isl and enabling graphite by default, but
> would suggest to enable it with -Ofast instead.
>
> One reason is that certainly extracting testcases from a PGO build is
> more difficult, and initially there will certa
I'm all in favour of requiring isl and enabling graphite by default, but would
suggest to enable it with -Ofast instead.
One reason is that certainly extracting testcases from a PGO build is more
difficult, and initially there will certainly be miscompiles with graphite
(CP2K is right now).
Sorry for not replying earlier, it seems gmail eats messages sometimes
(thus also not replying to the mail directly).
You write
> Since graphite will not modify the CFG when it does not do any
optimization,
> we would like to propose that graphite's polyhedral optimizer be enabled
at
> -O3 -fp
Since graphite will not modify the CFG when it does not do any optimization,
we would like to propose that graphite's polyhedral optimizer be enabled at
-O3 -fprofile-use where, compile time is of lesser concern.
gcc/ChangeLog:
2015-11-08 Aditya Kumar
Sebastian Pop
* gra
