From: Jakub Jelinek <jakub@redhat.com>
To: Marcel Vollweiler <marcel@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: [PATCH] OpenMP, libgomp: Add new runtime routines omp_target_memcpy_async and omp_target_memcpy_rect_async
Date: Thu, 19 May 2022 10:47:45 +0200 [thread overview]
Message-ID: <YoYEMQVk6JMpq/Dc@tucnak> (raw)
In-Reply-To: <f6239ed7-ab56-35c4-6b77-336ca6fbd6f1@codesourcery.com>
On Thu, May 19, 2022 at 10:39:05AM +0200, Marcel Vollweiler wrote:
> > add here
> > else
> > {
> > depend[0] = 0;
> > ...
> > }
>
> Added the "depend" definition to the "if" branch (instead the "else" branch).
Thanks for correcting my thinko.
> gcc/ChangeLog:
>
> * omp-low.cc (omp_runtime_api_call): Added target_memcpy_async and
> target_memcpy_rect_async to omp_runtime_apis array.
>
> libgomp/ChangeLog:
>
> * libgomp.map: Added omp_target_memcpy_async and
> omp_target_memcpy_rect_async.
> * libgomp.texi: Both functions are now supported.
> * omp.h.in: Added omp_target_memcpy_async and
> omp_target_memcpy_rect_async.
> * omp_lib.f90.in: Added interfaces for both new functions.
> * omp_lib.h.in: Likewise.
> * target.c (ialias_redirect): Added for GOMP_task.
> (omp_target_memcpy): Restructured into check and copy part.
> (omp_target_memcpy_check): New helper function for omp_target_memcpy and
> omp_target_memcpy_async that checks requirements.
> (omp_target_memcpy_copy): New helper function for omp_target_memcpy and
> omp_target_memcpy_async that performs the memcpy.
> (omp_target_memcpy_async_helper): New helper function that is used in
> omp_target_memcpy_async for the asynchronous task.
> (omp_target_memcpy_async): Added.
> (omp_target_memcpy_rect): Restructured into check and copy part.
> (omp_target_memcpy_rect_check): New helper function for
> omp_target_memcpy_rect and omp_target_memcpy_rect_async that checks
> requirements.
> (omp_target_memcpy_rect_copy): New helper function for
> omp_target_memcpy_rect and omp_target_memcpy_rect_async that performs
> the memcpy.
> (omp_target_memcpy_rect_async_helper): New helper function that is used
> in omp_target_memcpy_rect_async for the asynchronous task.
> (omp_target_memcpy_rect_async): Added.
> * task.c (ialias): Added for GOMP_task.
> * testsuite/libgomp.c-c++-common/target-memcpy-async-1.c: New test.
> * testsuite/libgomp.c-c++-common/target-memcpy-async-2.c: New test.
> * testsuite/libgomp.c-c++-common/target-memcpy-rect-async-1.c: New test.
> * testsuite/libgomp.c-c++-common/target-memcpy-rect-async-2.c: New test.
> * testsuite/libgomp.fortran/target-memcpy-async-1.f90: New test.
> * testsuite/libgomp.fortran/target-memcpy-async-2.f90: New test.
> * testsuite/libgomp.fortran/target-memcpy-rect-async-1.f90: New test.
> * testsuite/libgomp.fortran/target-memcpy-rect-async-2.f90: New test.
Ok, thanks.
Jakub
prev parent reply other threads:[~2022-05-19 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 11:19 Marcel Vollweiler
2022-05-05 8:30 ` Jakub Jelinek
2022-05-05 10:25 ` Tobias Burnus
[not found] ` <d549a138-c8f2-098b-39b1-c742cef5c534@codesourcery.com>
[not found] ` <YoPks36yV4Fbpb1m@tucnak>
2022-05-19 8:39 ` Marcel Vollweiler
2022-05-19 8:47 ` Jakub Jelinek [this message]
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=YoYEMQVk6JMpq/Dc@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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).