From: Tom de Vries <Tom_deVries@mentor.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: [PING^2][PATCH][3/3][PR65460] Mark offloaded functions as parallelized
Date: Mon, 08 Jun 2015 12:33:00 -0000 [thread overview]
Message-ID: <557588BA.6060409@mentor.com> (raw)
In-Reply-To: <5530DBA0.2000703@mentor.com>
On 17/04/15 12:08, Tom de Vries wrote:
> On 20-03-15 12:38, Tom de Vries wrote:
>> On 19-03-15 12:05, Tom de Vries wrote:
>>> On 18-03-15 18:22, Tom de Vries wrote:
>>>> Hi,
>>>>
>>>> this patch fixes PR65460.
>>>>
>>>> The patch marks offloaded functions as parallelized, which means the
>>>> parloops
>>>> pass no longer attempts to modify that function.
>>>
>>> Updated patch to postpone mark_parallelized_function until the
>>> corresponding
>>> cgraph_node is available, to ensure it works with the updated
>>> mark_parallelized_function from patch 2/3.
>>>
>>
>> Updated to eliminate mark_parallelized_function.
>>
>> Bootstrapped and reg-tested on x86_64.
>>
>> OK for stage4?
>>
>
> ping.
ping^2. Original post at
https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01063.html .
>
> OK for stage1?
>
Thanks,
- Tom
next prev parent reply other threads:[~2015-06-08 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 17:22 [PATCH][3/3][PR65460] " Tom de Vries
2015-03-19 11:05 ` Tom de Vries
2015-03-20 11:38 ` Tom de Vries
2015-03-21 22:31 ` Tom de Vries
2015-03-25 8:30 ` Thomas Schwinge
2015-04-17 10:08 ` [PING][PATCH][3/3][PR65460] " Tom de Vries
2015-06-08 12:33 ` Tom de Vries [this message]
2015-06-09 11:12 ` [PING^2][PATCH][3/3][PR65460] " Richard Biener
2015-06-09 14:12 ` Tom de Vries
2015-06-09 23:46 ` Thomas Schwinge
2015-06-10 8:26 ` Tom de Vries
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=557588BA.6060409@mentor.com \
--to=tom_devries@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).