On Mon, 16 May 2022, Tobias Burnus wrote:
> Hi all,
>
> I would like to ping the following patches from Frederik's
> "[PATCH 00/40] OpenACC "kernels" Improvements" series
> https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586901.html
> patch set thread link:
>
Hi all,
I would like to ping the following patches from Frederik's
"[PATCH 00/40] OpenACC "kernels" Improvements" series
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586901.html
patch set thread link:
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/thread.html#586901
(A)
On Sat, Nov 15, 2014 at 11:57 AM, Mircea Namolaru
mircea.namol...@inria.fr 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
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
hardly
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
