From: Michael Ploujnikov <michael.ploujnikov@oracle.com>
To: Martin Jambor <mjambor@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: [PING v2][PATCH] Make function clone name numbering independent.
Date: Wed, 05 Sep 2018 03:32:00 -0000 [thread overview]
Message-ID: <7b66290c-dc1f-9f0f-f0c0-caab48d25f1a@oracle.com> (raw)
In-Reply-To: <ri636uqlx0q.fsf@suse.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1740 bytes --]
Hi Martin,
On 2018-09-03 06:01 AM, Martin Jambor wrote:
> Hi,
>
> On Fri, Aug 31 2018, Michael Ploujnikov wrote:
>> I've done some more digging into the current uses of
>> numbered_clone_function_name and checked if any tests fail if I change
>> it to suffixed_function_name:
>>
>> - gcc/cgraphclones.c: DECL_NAME (new_decl) = numbered_clone_function_name (thunk->decl, "artificial_thunk");
>> - no new tests fail, inconclusive
>> - and despite the comment on redirect_callee_duplicating_thunks
>> about "one or more" duplicates it doesn't seem like
>> duplicate_thunk_for_node would be called more than once for each
>> node, assuming each node is named uniquely, but I'm far from an
>> expert in this area
>
> The comment means that if there is a chain of thunks, the method clones
> all of them. Nevertheless, you need name numbering here for the same
> reason why you need them for constprop.
>
>
>> - gcc/omp-expand.c: DECL_NAME (kern_fndecl) = numbered_clone_function_name (kern_fndecl, "kernel");
>> - no new tests fail, inconclusive
>> - I didn't see (and couldn't figure out a way to get) any of the
>> existing omp/acc tests actually exercise this codeptah
>
> I guess this one should not need it. Build with
> --enable-offload-targets=hsa and run gomp.exp to try yourself. I can
> run run-time HSA tests for you if you want.
>
> Martin
>
I've tried building with numbered_clone_function_name replaced by
suffixed_function_name and with --enable-offload-targets=hsa and
didn't see any errors in gomp.exp. I don't have a readily available
HSA setup so if you could do a quick test, I would really appreciate
it!
- Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2018-09-05 3:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 19:38 [PATCH] " Michael Ploujnikov
2018-07-17 6:10 ` Bernhard Reutner-Fischer
2018-07-17 10:03 ` Richard Biener
2018-07-17 20:25 ` Michael Ploujnikov
2018-07-20 2:49 ` Michael Ploujnikov
2018-07-20 10:05 ` Richard Biener
2018-07-24 13:57 ` Michael Ploujnikov
2018-07-26 17:27 ` Michael Ploujnikov
2018-07-31 17:40 ` Michael Ploujnikov
2018-08-01 10:38 ` Richard Biener
2018-08-02 19:05 ` Michael Ploujnikov
2018-08-13 23:58 ` [PING][PATCH] " Michael Ploujnikov
2018-08-20 19:47 ` Jeff Law
2018-08-31 18:49 ` [PING v2][PATCH] " Michael Ploujnikov
2018-09-03 10:02 ` Martin Jambor
2018-09-03 11:08 ` Richard Biener
2018-09-03 13:15 ` Martin Jambor
2018-09-05 3:24 ` Michael Ploujnikov
2018-11-28 21:09 ` [PATCH v3] " Michael Ploujnikov
2018-11-28 22:49 ` Segher Boessenkool
2018-11-29 14:13 ` Michael Ploujnikov
2018-11-30 7:26 ` Richard Biener
2018-11-30 21:11 ` Michael Ploujnikov
2018-12-01 16:31 ` H.J. Lu
2018-12-03 17:00 ` Michael Ploujnikov
2018-12-04 3:06 ` Michael Ploujnikov
2018-12-04 14:07 ` Jan Hubicka
2018-09-05 3:32 ` Michael Ploujnikov [this message]
2018-12-04 12:48 ` [PING v2][PATCH] " Martin Jambor
2018-12-04 13:22 ` Michael Ploujnikov
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=7b66290c-dc1f-9f0f-f0c0-caab48d25f1a@oracle.com \
--to=michael.ploujnikov@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
/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).