https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61121
--- Comment #4 from Jim Michaels <jmichae3 at yahoo dot com> ---
which means to me it takes only a constant.
it should be able to take the equivalent of "auto" (however the gcc folk want
to write that), again due to the wide difference between processors. for
targeting public machines, you can't assume they are all the same (can't assume
they all have 4 threads - some machines are dual-core).
I *think* the value 0 does the equivalent of auto, but still testing this. if
this is working, it should be documented as such.
-ftree-parallelize-loops=@var{n}
is not in the manual.
alsdo, according to the HTML documentation at
https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcc/Optimize-Options.html#Optimize-Options
n is not in a different font.
