public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom de Vries <Tom_deVries@mentor.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
	Richard Biener <rguenther@suse.de>
Subject: [PATCH][3/3][PR65460] Mark offloaded functions as parallelized
Date: Wed, 18 Mar 2015 17:22:00 -0000	[thread overview]
Message-ID: <5509B43E.802@mentor.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 237 bytes --]

Hi,

this patch fixes PR65460.

The patch marks offloaded functions as parallelized, which means the parloops 
pass no longer attempts to modify that function.

Bootstrapped and reg-tested on x86_64.

OK for stage4 trunk?

Thanks,
- Tom

[-- Attachment #2: 0003-Mark-offloaded-functions-as-parallelized.patch --]
[-- Type: text/x-patch, Size: 682 bytes --]

Mark offloaded functions as parallelized

2015-03-18  Tom de Vries  <tom@codesourcery.com>

	PR tree-optimization/65460
	* omp-low.c (expand_omp_target): Call mark_parallelized_function for
	child_fn.
---
 gcc/omp-low.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/omp-low.c b/gcc/omp-low.c
index c5c0ccf..e7ceee2 100644
--- a/gcc/omp-low.c
+++ b/gcc/omp-low.c
@@ -8801,6 +8801,7 @@ expand_omp_target (struct omp_region *region)
     {
       child_fn = gimple_omp_target_child_fn (entry_stmt);
       child_cfun = DECL_STRUCT_FUNCTION (child_fn);
+      mark_parallelized_function (child_fn);
     }
 
   /* Supported by expand_omp_taskreg, but not here.  */
-- 
1.9.1


             reply	other threads:[~2015-03-18 17:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 17:22 Tom de Vries [this message]
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       ` [PING^2][PATCH][3/3][PR65460] " Tom de Vries
2015-06-09 11:12         ` 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=5509B43E.802@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).