> New optimization flags and new params need documentation in
> gcc/doc/invoke.texi.
>
Thanks. Added description in invoke.texi. The patch is in trunk.
> The description of the --params suggest they provide fixed values - is
> there no way to autodetect sensible values with a cost-model? I
> ha
On Sat, Nov 15, 2014 at 11:57 AM, Mircea Namolaru
wrote:
> The close of stage 1 is getting close (very close). Even there is not so much
> new code (basically
> the new code computes the separation class option for AST build), I am not
> sure that the patch
> qualify for stage 2.
>
> There is ve
The close of stage 1 is getting close (very close). Even there is not so much
new code (basically
the new code computes the separation class option for AST build), I am not sure
that the patch
qualify for stage 2.
There is very nice code generated by unroll-and-jam (stride mining) for small
ke
