On 14/09/15 10:52, Bernd Schmidt wrote:
I'm curious why
this would be a param rather than a -f option.
Hi Bernd,
parloops-chunk-size is also a param, so I think it would make sense to
have parloops-schedule as a param as well.
[ So, in order for parloops to generate:
#pragma omp for sche
On 14/09/15 16:28, Tom de Vries wrote:
On 14/09/15 11:09, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 03:28:01PM +0200, Tom de Vries wrote:
On 11/09/15 12:57, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
Hi,
this patch adds a param parloops-schedule=<0-
On 14/09/15 11:09, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 03:28:01PM +0200, Tom de Vries wrote:
On 11/09/15 12:57, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
Hi,
this patch adds a param parloops-schedule=<0-4>, which sets the omp schedule
for loop
On Fri, Sep 11, 2015 at 03:28:01PM +0200, Tom de Vries wrote:
> On 11/09/15 12:57, Jakub Jelinek wrote:
> >On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
> >>>Hi,
> >>>
> >>>this patch adds a param parloops-schedule=<0-4>, which sets the omp
> >>>schedule
> >>>for loops paralellized
On 09/11/2015 03:28 PM, Tom de Vries wrote:
This patch adds handling of a DEFPARAMENUM macro, which is similar to
the DEFPARAM macro, but allows the values to be named.
So the definition of param parloop-schedule becomes:
...
DEFPARAMENUM PARAM_PARLOOPS_SCHEDULE,
"parloops-schedul
On 11/09/15 15:28, Tom de Vries wrote:
So the definition of param parloop-schedule becomes:
...
DEFPARAMENUM PARAM_PARLOOPS_SCHEDULE,
"parloops-schedule",
"Schedule type of omp schedule for loops parallelized by "
"parloops (static, dynamic, guided, auto,
On 11/09/15 12:57, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
>Hi,
>
>this patch adds a param parloops-schedule=<0-4>, which sets the omp schedule
>for loops paralellized by parloops.
>
>The <0-4> maps onto .
>
>Bootstrapped and reg-tested on x86_64.
>
>OK
On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
> Hi,
>
> this patch adds a param parloops-schedule=<0-4>, which sets the omp schedule
> for loops paralellized by parloops.
>
> The <0-4> maps onto .
>
> Bootstrapped and reg-tested on x86_64.
>
> OK for trunk?
I don't really like