From: Jeff Law <law@redhat.com>
To: Tom de Vries <Tom_deVries@mentor.com>,
"gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: Re: [patch, driver] Ignore -ftree-parallelize-loops={0,1}
Date: Tue, 14 Jul 2015 04:55:00 -0000 [thread overview]
Message-ID: <55A49620.9070501@redhat.com> (raw)
In-Reply-To: <55A399D8.60300@mentor.com>
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-parallelize-loops=*:-pthread}"
>> ...
>>
>> Actually, ftree-parallelize-loops={0,1} means that no parallelization is
>> done, but these spec strings still get activated for these values.
>>
>>
>> Attached patch fixes that, by introducing a spec function gt (short for
>> greather than), and using it in the spec lines.
>>
>
> Attached (untested) patch manages the same, without introducing the spec
> function 'gt'. But the solution is a bit convoluted, so I prefer the one
> with the gt function.
I prefer the one with the gt function :-)
jeff
next prev parent reply other threads:[~2015-07-14 4:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 7:54 Tom de Vries
2015-07-13 10:58 ` Tom de Vries
2015-07-14 4:55 ` Jeff Law [this message]
2015-07-14 8:36 ` Tom de Vries
2016-03-17 16:28 ` Thomas Schwinge
2016-04-08 10:36 ` Thomas Schwinge
2016-04-08 11:39 ` Tom de Vries
2016-04-08 11:44 ` Jakub Jelinek
2016-04-08 13:48 ` Thomas Schwinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55A49620.9070501@redhat.com \
--to=law@redhat.com \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).