Hi!
On Fri, 5 Oct 2018 21:03:36 +0100, Julian Brown wrote:
> Continuing the thread from here:
>
> https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00198.html
>
> On Wed, 3 Feb 2016 19:52:09 +0300
> Alexander Monakov wrote:
>
> > On Wed, 3 Feb 2016, Nathan Sidwell wrote:
> > > You can only overri
Hi,
Continuing the thread from here:
https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00198.html
On Wed, 3 Feb 2016 19:52:09 +0300
Alexander Monakov wrote:
> On Wed, 3 Feb 2016, Nathan Sidwell wrote:
> > You can only override at runtime those dimensions that you said
> > you'd override at runtime
On Wed, 3 Feb 2016, Nathan Sidwell wrote:
> You can only override at runtime those dimensions that you said you'd override
> at runtime when you compiled your program.
Ah, I see. That's not obvious to me, so perhaps added documentation can be
expanded to explain that? (I now see that the plugin
On 02/03/16 11:10, Alexander Monakov wrote:
Hello,
On Wed, 3 Feb 2016, Nathan Sidwell wrote:
1) extend the -fopenacc-dim=X:Y:Z syntax to allow '-' indicating a runtime
choice. (0 also indicates that, but I thought best to have an explicit syntax
as well).
Does it work when the user specifies
Hello,
On Wed, 3 Feb 2016, Nathan Sidwell wrote:
> 1) extend the -fopenacc-dim=X:Y:Z syntax to allow '-' indicating a runtime
> choice. (0 also indicates that, but I thought best to have an explicit syntax
> as well).
Does it work when the user specifies one of the dimensions, so that references
Jakub,
this is the runtime side of default compute dimension support.
1) extend the -fopenacc-dim=X:Y:Z syntax to allow '-' indicating a runtime
choice. (0 also indicates that, but I thought best to have an explicit syntax
as well).
2) New plugin helper 'GOMP_PLUGIN_acc_default_dims' that pa
