public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
	Jakub Jelinek <jakub@redhat.com>,
	Andrew Stubbs <ams@codesourcery.com>
Cc: "Vollweiler, Marcel" <marcel@codesourcery.com>
Subject: *ping* / Re: [Patch] libgomp: Add offload_device_gcn check, add requires-4a.c test
Date: Mon, 17 Oct 2022 09:36:58 +0200	[thread overview]
Message-ID: <419bf239-6672-8d64-e3e3-bfe3196f7878@codesourcery.com> (raw)
In-Reply-To: <ebcb6977-c445-264e-ce06-d56beb4bbcc0@codesourcery.com>


On 12.10.22 16:05, Tobias Burnus wrote:
> This came up because the USM implementation with
> -foffload-memory={unified,pinned}
> as posted at
> https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597976.html
> does not handle USM with static variables.
>
> This shows up for the OG12 alias devel/omp/gcc-12 branch as FAIL for
> requires-4.c.
>
> The attached patch prepares for skipping requires-4.c for the
> gcn/nvptx device
> and adds an adjacent requires-4a.c testcase, using heap memory, that
> can still
> run on gcn/nvptx.
>
> Additionally, I commented on no longer used #defined, following the
> precedence GOMP_DEVICE_HOST_NONSHM.
>
> Thus, this tests adds another testcase and one effective-target check,
> out-comments a unused #define - and that's it.
> (Otherwise, it is just a prep patch.)
>
> OK for mainline?
>
> Tobias
>
> PS: Currently, neither the preexisting offload_device_nvptx nor the new
> offload_device_gcn target selector is used, neither in old code nor by
> this patch.
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  reply	other threads:[~2022-10-17  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 14:05 Tobias Burnus
2022-10-17  7:36 ` Tobias Burnus [this message]
2022-10-20 10:46 ` Jakub Jelinek

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=419bf239-6672-8d64-e3e3-bfe3196f7878@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=marcel@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).