| 1 |
On Sun, Apr 30, 2017 at 11:34:44PM +0300, Nikos Chantziaras wrote |
| 2 |
> On 04/30/2017 10:36 PM, Walter Dnes wrote: |
| 3 |
> > |
| 4 |
> > For Pale Moon, the developers want... |
| 5 |
> > |
| 6 |
> > -floop-parallelize-all -fpredictive-commoning -ftree-loop-distribution -ftree-vectorize |
| 7 |
> > |
| 8 |
> > I follow those specs when doing a contributed build. |
| 9 |
> |
| 10 |
> Are these using graphite though? |
| 11 |
|
| 12 |
Yes. Non-graphite GCC errors out if I include them in |
| 13 |
CFLAGS/CXXFLAGS. Try for yourself. Include those flags, if you don't |
| 14 |
have graphite, and try to build something. See also |
| 15 |
https://gcc.gnu.org/wiki/Graphite/Parallelization |
| 16 |
|
| 17 |
> First step of autopar in Graphite has been done. You can trigger it |
| 18 |
> by 2 flags -floop-parallelize-all -ftree-parallelize-loops=4. Both |
| 19 |
> of them is needed, the first flag will trigger Graphite pass to mark |
| 20 |
> loops that can be parallel and the second flag will trigger the code |
| 21 |
> generation part. |
| 22 |
|
| 23 |
-- |
| 24 |
Walter Dnes <waltdnes@××××××××.org> |
| 25 |
I don't run "desktop environments"; I run useful applications |
Archives