Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2016-04-08 Thread Thomas Schwinge
Hi! On Fri, 8 Apr 2016 13:43:49 +0200, Jakub Jelinek wrote: > On Fri, Apr 08, 2016 at 01:38:06PM +0200, Tom de Vries wrote: > > On 08/04/16 12:35, Thomas Schwinge wrote: > > I've looked at the patch, it looks good to me. > > > > I think it can be committed as obvious. > > The patch is ok for tr

Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2016-04-08 Thread Jakub Jelinek
On Fri, Apr 08, 2016 at 01:38:06PM +0200, Tom de Vries wrote: > On 08/04/16 12:35, Thomas Schwinge wrote: > I've looked at the patch, it looks good to me. > > I think it can be committed as obvious. The patch is ok for trunk. > >>commit df7d7943ae64f6df74d360e71f7c495c78647fda > >>Author: Thomas

Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2016-04-08 Thread Tom de Vries
On 08/04/16 12:35, Thomas Schwinge wrote: Hi! Ping. On Thu, 17 Mar 2016 17:24:48 +0100, I wrote: On Tue, 14 Jul 2015 10:36:25 +0200, Tom de Vries wrote: On 14/07/15 06:54, Jeff Law wrote: On 07/13/2015 04:58 AM, Tom de Vries wrote: On 07/07/15 09:53, Tom de Vries wrote: currently, we have

Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2016-04-08 Thread Thomas Schwinge
Hi! Ping. On Thu, 17 Mar 2016 17:24:48 +0100, I wrote: > On Tue, 14 Jul 2015 10:36:25 +0200, Tom de Vries > wrote: > > On 14/07/15 06:54, Jeff Law wrote: > > > On 07/13/2015 04:58 AM, Tom de Vries wrote: > > >> On 07/07/15 09:53, Tom de Vries wrote: > > >>> currently, we have these spec strings

Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2016-03-19 Thread Thomas Schwinge
Hi! On Tue, 14 Jul 2015 10:36:25 +0200, Tom de Vries wrote: > On 14/07/15 06:54, Jeff Law wrote: > > On 07/13/2015 04:58 AM, Tom de Vries wrote: > >> On 07/07/15 09:53, Tom de Vries wrote: > >>> currently, we have these spec strings in gcc/gcc.c involving > >>> ftree-parallelize-loops: > >>> ...

Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2015-07-14 Thread Tom de Vries
On 14/07/15 06:54, Jeff Law wrote: On 07/13/2015 04:58 AM, Tom de Vries wrote: On 07/07/15 09:53, Tom de Vries wrote: Hi, currently, we have these spec strings in gcc/gcc.c involving ftree-parallelize-loops: ... %{fopenacc|fopenmp|ftree-parallelize-loops=*:%:include(libgomp.spec)%(link_gomp)}

Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2015-07-13 Thread Jeff Law
On 07/13/2015 04:58 AM, Tom de Vries wrote: On 07/07/15 09:53, Tom de Vries wrote: Hi, currently, we have these spec strings in gcc/gcc.c involving ftree-parallelize-loops: ... %{fopenacc|fopenmp|ftree-parallelize-loops=*:%:include(libgomp.spec)%(link_gomp)} %{fopenacc|fopenmp|ftree-paralleli

Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}

2015-07-13 Thread Tom de Vries
On 07/07/15 09:53, Tom de Vries wrote: Hi, currently, we have these spec strings in gcc/gcc.c involving ftree-parallelize-loops: ... %{fopenacc|fopenmp|ftree-parallelize-loops=*:%:include(libgomp.spec)%(link_gomp)} %{fopenacc|fopenmp|ftree-parallelize-loops=*:-pthread}" ... Actually, ftree-par

[patch, driver] Ignore -ftree-parallelize-loops={0,1}

2015-07-07 Thread Tom de Vries
Hi, currently, we have these spec strings in gcc/gcc.c involving ftree-parallelize-loops: ... %{fopenacc|fopenmp|ftree-parallelize-loops=*:%:include(libgomp.spec)%(link_gomp)} %{fopenacc|fopenmp|ftree-parallelize-loops=*:-pthread}" ... Actually, ftree-parallelize-loops={0,1} means that no para