From: Sandra Loosemore <sandra@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>
Cc: Jan Hubicka <jh@suse.cz>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3] Re: OpenMP: Generate SIMD clones for functions with "declare target"
Date: Thu, 27 Oct 2022 14:40:13 -0600 [thread overview]
Message-ID: <22d22939-2f6b-c14a-17fc-834547c05f96@codesourcery.com> (raw)
In-Reply-To: <871qqtd1cy.fsf@dem-tschwing-1.ger.mentorg.com>
On 10/27/22 04:09, Thomas Schwinge wrote:
> Hi!
>
> On 2022-10-26T20:27:19-0600, Sandra Loosemore <sandra@codesourcery.com> wrote:
>> One of my test cases examines the .s output to make sure that the clones
>> are emitted as local symbols and not global. I have not been able to
>> find the symbol linkage information in any of the dump files
>
> Hmm, also some of '-fdump-ipa-all-details' doesn't help here?
Maybe I'm not looking at the right dump file, but all I see is names of
functions in the dumps and nothing about symbol linkage/visibility, even
with -details.
> And/or, where you implement the logic to "make sure that the clones
> are emitted as local symbols and not global", do emit some "tag" in the
> dump file, and the scan for that?
>
> Random examples that I just remembered:
>
> 'gcc/omp-offload.cc:execute_oacc_loop_designation' handling of
> 'OMP_CLAUSE_NOHOST', and how that's scanned (host-side) in test cases
> such as 'libgomp/testsuite/libgomp.oacc-c-c++-common/routine-nohost-1.c',
> 'libgomp/testsuite/libgomp.oacc-fortran/routine-nohost-1.f90'.
>
> 'gcc/config/nvptx/nvptx.cc:nvptx_find_sese' doing
> 'fprintf (dump_file, "SESE regions:"); [...]', and that's scanned in:
>
> libgomp/testsuite/libgomp.oacc-c-c++-common/nvptx-sese-1.c-/* Match {N->N(.N)+} */
> libgomp/testsuite/libgomp.oacc-c-c++-common/nvptx-sese-1.c:/* { dg-final { scan-offload-rtl-dump "SESE regions:.* \[0-9\]+{\[0-9\]+->\[0-9\]+(\\.\[0-9\]+)+}" "mach" } } */
>
> (You'd be doing this at the 'scan-offload-tree-dump[...]' level, I
> suppose.)
I guess customizing the dump output from the simdclone pass with the
information I need is the easiest solution. I'm still concerned about
getting adequate routine test coverage, though, when it's so specialized
to a particular offload target.
Thanks for the help! :-)
-Sandra
next prev parent reply other threads:[~2022-10-27 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 17:32 Sandra Loosemore
2022-09-14 18:12 ` Jakub Jelinek
2022-09-22 3:17 ` [PATCH v2] " Sandra Loosemore
2022-09-30 10:37 ` Jakub Jelinek
2022-10-17 1:23 ` [PATCH v3] " Sandra Loosemore
2022-10-20 14:07 ` Jakub Jelinek
2022-10-27 2:27 ` Sandra Loosemore
2022-10-27 10:09 ` Thomas Schwinge
2022-10-27 20:40 ` Sandra Loosemore [this message]
2022-09-14 21:45 ` 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=22d22939-2f6b-c14a-17fc-834547c05f96@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jh@suse.cz \
--cc=thomas@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).