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>,
	fortran <fortran@gcc.gnu.org>,	Jakub Jelinek <jakub@redhat.com>
Subject: *ping* Re: [Patch][OpenMP] use_device_addr/use_device_ptr with Fortran allocatable/pointer arrays (= array descriptor)
Date: Wed, 23 Oct 2019 07:08:00 -0000	[thread overview]
Message-ID: <bab1ba79-b6b2-236a-02c7-a4ed9d75fb3b@codesourcery.com> (raw)
In-Reply-To: <7b38dcfe-7510-59f1-f6aa-1735abc340c8@codesourcery.com>

*ping*

On 10/14/19 3:11 PM, Tobias Burnus wrote:
> This is a follow-up patch to the use_device_addr work. In particular, 
> it replaces the patch at 
> https://gcc.gnu.org/ml/fortran/2019-09/msg00088.html
>
> Fortran array descriptors need special handling, which this patch adds.
>
> [The use_device-addr-{3,4} test cases are based on the 
> use_device_addr-{1,2} ones; I saw that I could have tested there 
> optional + deallocated in addition, hence, I added it as well (to all 
> four files). – The use_device-ptr-1.f90 is a slightly cleaned-up 
> version of previous patch and I have removed the compile-time checks 
> of previous patch.]
>
> Bootstrapped + regtested on x86_64-gnu-linux w/o "device". And tested 
> additionally the testcases with nvptx offloading.
>
> Thanks,
>
> Tobias
>

  reply	other threads:[~2019-10-23  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 13:17 Tobias Burnus
2019-10-23  7:08 ` Tobias Burnus [this message]
2019-10-30 10:46 ` Jakub Jelinek
2019-10-31 17:10   ` Tobias Burnus
2019-10-31 18:02     ` Jakub Jelinek
2019-11-11  9:16     ` 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=bab1ba79-b6b2-236a-02c7-a4ed9d75fb3b@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --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).