From: Chung-Lin Tang <chunglin_tang@mentor.com>
To: Julian Brown <julian@codesourcery.com>, <gcc-patches@gcc.gnu.org>
Cc: Andrew Stubbs <andrew_stubbs@mentor.com>
Subject: Re: [PATCH 2/6] [og9] OpenACC middle-end worker-partitioning support
Date: Thu, 05 Sep 2019 13:52:00 -0000 [thread overview]
Message-ID: <499c97e1-236a-1810-74f3-c98066c2a59e@mentor.com> (raw)
In-Reply-To: <1de0113e1a6807da85e5c7b0f7d473234f78dd45.1567644180.git.julian@codesourcery.com>
On 2019/9/5 9:45 AM, Julian Brown wrote:
> Much of omp-sese.c originates from code written for NVPTX by Nathan
> Sidwell (adapted to work on gimple instead of RTL) -- though at present,
> only the per-basic-block scheme is implemented, and the SESE-finding
> algorithm isn't yet used.
Hi Julian,
it appears that this part broke NVPTX builds due to the duplicate stuff in
config/nvptx/nvptx.c and the new omp-sese.c file (e.g. struct parallel).
Can you fix this? (being able to factor away stuff from nvptx backend into
the middle-end seems a good idea in general)
Thanks,
Chung-Lin
next prev parent reply other threads:[~2019-09-05 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 1:46 [PATCH 0/6] [og9] OpenACC worker partitioning in middle end (AMD GCN) Julian Brown
2019-09-05 1:46 ` [PATCH 4/6] [og9] Fix up tests for oaccdevlow pass splitting Julian Brown
2019-09-05 1:46 ` [PATCH 1/6] [og9] Target-dependent gang-private variable decl rewriting Julian Brown
2019-09-05 1:46 ` [PATCH 2/6] [og9] OpenACC middle-end worker-partitioning support Julian Brown
2019-09-05 13:52 ` Chung-Lin Tang [this message]
2019-09-05 15:01 ` Julian Brown
2019-09-06 12:32 ` Julian Brown
2019-09-05 1:46 ` [PATCH 3/6] [og9] AMD GCN adjustments for middle-end worker partitioning Julian Brown
2019-09-05 1:47 ` [PATCH 5/6] [og9] Reference reduction localization Julian Brown
2019-09-05 1:47 ` [PATCH 6/6] [og9] Enable worker partitioning for AMD GCN Julian Brown
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=499c97e1-236a-1810-74f3-c98066c2a59e@mentor.com \
--to=chunglin_tang@mentor.com \
--cc=andrew_stubbs@mentor.com \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=julian@codesourcery.com \
/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).