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>
Subject: *ping* Re: [Patch] OpenMP: Fix reverse offload GOMP_TARGET_REV IFN corner cases [PR107236]
Date: Mon, 24 Oct 2022 09:47:31 +0200	[thread overview]
Message-ID: <7cc0ce4b-90b0-8182-d7e8-5c21e61fc72c@codesourcery.com> (raw)
In-Reply-To: <9e2d0331-92c4-c8a6-a662-61f298fb3976@codesourcery.com>

Ping this patch – and also "Re: [Patch][v5] libgomp/nvptx: Prepare for
reverse-offload callback handling".

For the latter cf. Alexander's code approval
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603908.html – and
his concerns regarding the generic feature in
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601959.html (I
think 'target nowait' permits what he thinks is the better way for GPUs.)

Tobias

On 18.10.22 21:27, Tobias Burnus wrote:
> Found when playing around with reverse offload once I used 'omp target
> parallel'.
> The other issue showed up when running the testsuite (which is done
> with -O2).
>
> In all cases, the ICE is in expand_GOMP_TARGET_REV of this IFN, which
> should
> be unreachable
>
> Note: ENABLE_OFFLOADING inside the compiler must evaluate to true to
> show up
> as ICE - otherwise, the IFN is not even generated.
>
> I did not see a good reason for DECL_CONTEXT = NULL, thus, I now set
> it to
> the same as was set for child_fn - for no good reason.
>
> Tested on x86-64 with ENABLE_OFFLOADING albeit without true offloading.
> OK for mainline?
>
> Tobias
-----------------
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-24  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 19:27 Tobias Burnus
2022-10-24  7:47 ` Tobias Burnus [this message]
2022-10-24 13:14 ` 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=7cc0ce4b-90b0-8182-d7e8-5c21e61fc72c@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).