Re: Default compute dimensions (runtime)

2019-04-25 Thread Thomas Schwinge
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

Re: Default compute dimensions

2019-01-30 Thread Thomas Schwinge
Hi! On Thu, 28 Jan 2016 10:38:51 -0500, Nathan Sidwell wrote: > This patch adds default compute dimension handling. [...] > --- gcc/doc/invoke.texi (revision 232881) > +++ gcc/doc/invoke.texi (working copy) > @@ -1963,9 +1963,13 @@ Programming Interface v2.0 @w{@uref{http > implies

Re: Default compute dimensions (runtime)

2018-10-05 Thread Julian Brown
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

Re: Default compute dimensions (runtime)

2016-02-03 Thread Alexander Monakov
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

Re: Default compute dimensions (runtime)

2016-02-03 Thread Nathan Sidwell
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

Re: Default compute dimensions (runtime)

2016-02-03 Thread Alexander Monakov
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

Re: Default compute dimensions

2016-02-01 Thread Nathan Sidwell
On 02/01/16 13:42, Jakub Jelinek wrote: Your patch broke bootstrap on ILP32 hosts, I'm testing following fix. Supporting unsigned values from 0x8000U to 0xU only on LP64 hosts and not on ILP64 hosts sounds really weird, I think it is better to only support 1 to 0x7fffU. yes, I

Re: Default compute dimensions

2016-02-01 Thread H.J. Lu
On Mon, Feb 1, 2016 at 8:15 AM, Nathan Sidwell wrote: > On 02/01/16 10:32, Jakub Jelinek wrote: >> >> On Mon, Feb 01, 2016 at 09:15:05AM -0500, Nathan Sidwell wrote: >>> >>> On 01/29/16 10:18, Jakub Jelinek wrote: On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote: >

Re: Default compute dimensions

2016-02-01 Thread Jakub Jelinek
On Mon, Feb 01, 2016 at 11:15:13AM -0500, Nathan Sidwell wrote: > On 02/01/16 10:32, Jakub Jelinek wrote: > >On Mon, Feb 01, 2016 at 09:15:05AM -0500, Nathan Sidwell wrote: > >>On 01/29/16 10:18, Jakub Jelinek wrote: > >>>On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote: > This pa

Re: Default compute dimensions

2016-02-01 Thread Nathan Sidwell
On 02/01/16 10:32, Jakub Jelinek wrote: On Mon, Feb 01, 2016 at 09:15:05AM -0500, Nathan Sidwell wrote: On 01/29/16 10:18, Jakub Jelinek wrote: On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote: This patch adds default compute dimension handling. Users rarely specify compute dime

Re: Default compute dimensions

2016-02-01 Thread Jakub Jelinek
On Mon, Feb 01, 2016 at 09:15:05AM -0500, Nathan Sidwell wrote: > On 01/29/16 10:18, Jakub Jelinek wrote: > >On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote: > >>This patch adds default compute dimension handling. Users rarely specify > >>compute dimensions, expecting the toolchain

Re: Default compute dimensions

2016-02-01 Thread Nathan Sidwell
On 01/29/16 10:18, Jakub Jelinek wrote: On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote: This patch adds default compute dimension handling. Users rarely specify compute dimensions, expecting the toolchain to DTRT. More savvy users would like to specify global defaults. This pa

Re: Default compute dimensions

2016-01-29 Thread Nathan Sidwell
On 01/29/16 10:18, Jakub Jelinek wrote: On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote: This patch adds default compute dimension handling. Users rarely specify compute dimensions, expecting the toolchain to DTRT. More savvy users would like to specify global defaults. This pa

Re: Default compute dimensions

2016-01-29 Thread Jakub Jelinek
On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote: > This patch adds default compute dimension handling. Users rarely specify > compute dimensions, expecting the toolchain to DTRT. More savvy users would > like to specify global defaults. This patch permits both. Isn't it better to