public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/104423] [libgomp, testsuite] Add means to do accelerator-only testing in libgomp
Date: Tue, 08 Feb 2022 14:47:03 +0000	[thread overview]
Message-ID: <bug-104423-4-3Tyf1Um42c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104423-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #2)
> For OpenMP test cases, we'd either have to manually mark them up (error
> prone and generally ugly), or scan the source file(s) (error prone and
> generally ugly), or use some kind of marker that gets set during compilation
> if any offloading code has been generated.

I was thinking along the lines of already existing markers in the exec:
...
$ nm for-3.exe | grep offload
                 U GOMP_offload_register_ver
                 U GOMP_offload_unregister_ver
0000000000a59718 D __offload_funcs_end
0000000000a58a58 d .offload_func_table
0000000000a58a58 D __offload_func_table
0000000000a5ca38 D __offload_vars_end
0000000000a59718 d .offload_var_table
0000000000a59718 D __offload_var_table
...

Say, if the exec doesn't have a __offload_func_table, it can be skipped.

This would allow to do one test run, where you run all the tests, and generate
the offloading tests list, and then several more runs (using the same sources,
so the list is still up to date) where you just do the accelerator tests.

  parent reply	other threads:[~2022-02-08 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 15:43 [Bug testsuite/104423] New: " vries at gcc dot gnu.org
2022-02-08 12:32 ` [Bug testsuite/104423] " vries at gcc dot gnu.org
2022-02-08 14:15 ` tschwinge at gcc dot gnu.org
2022-02-08 14:47 ` vries at gcc dot gnu.org [this message]
2022-02-11 14:59 ` vries at gcc dot gnu.org
2022-02-14 16:14 ` vries at gcc dot gnu.org
2022-05-29  5:11 ` egallager at gcc dot gnu.org

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=bug-104423-4-3Tyf1Um42c@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).