From: Tom de Vries <tdevries@suse.de>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Alexander Monakov <amonakov@ispras.ru>,
Jakub Jelinek <jakub@redhat.com>,
Andrew Stubbs <ams@codesourcery.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][libgomp, nvptx] Fix hang in gomp_team_barrier_wait_end
Date: Thu, 20 May 2021 13:41:01 +0200 [thread overview]
Message-ID: <7e88d3c6-b0d5-8356-e20e-c560513fe455@suse.de> (raw)
In-Reply-To: <875yzdbukx.fsf@euler.schwinge.homeip.net>
On 5/20/21 11:52 AM, Thomas Schwinge wrote:
> Hi Tom!
>
> First, thanks for looking into this PR99555!
>
>
> I can't comment on the OpenMP/nvptx changes, so just the following:
>
> On 2021-04-23T18:48:01+0200, Tom de Vries <tdevries@suse.de> wrote:
>> --- a/libgomp/testsuite/libgomp.fortran/task-detach-6.f90
>> +++ b/libgomp/testsuite/libgomp.fortran/task-detach-6.f90
>> @@ -1,6 +1,5 @@
>> ! { dg-do run }
>>
>> -! { dg-additional-sources on_device_arch.c }
>> ! { dg-prune-output "command-line option '-fintrinsic-modules-path=.*' is valid for Fortran but not for C" }
>
> Please remove the 'dg-prune-output', too. ;-)
>
Ack, updated patch.
> Your changes leave
> 'libgomp/testsuite/lib/libgomp.exp:check_effective_target_offload_device_nvptx',
> 'libgomp/testsuite/libgomp.c-c++-common/on_device_arch.h',
> 'libgomp/testsuite/libgomp.fortran/on_device_arch.c' unused. Should we
> keep those for a potential future use (given that they've been tested to
> work) or remove (as now unused, danger of bit-rot)?
I vote to leave them in, they look useful, and I think the danger of
bit-rot is less than the danger of not knowing/remembering that they
once where there and having to start from scratch.
Thanks,
- Tom
next prev parent reply other threads:[~2021-05-20 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 11:23 Tom de Vries
2021-04-20 16:11 ` Alexander Monakov
2021-04-21 16:10 ` Tom de Vries
2021-04-21 17:02 ` Alexander Monakov
2021-04-22 11:11 ` Tom de Vries
2021-04-23 15:45 ` Alexander Monakov
2021-04-23 16:48 ` Tom de Vries
2021-05-19 14:52 ` [PING][PATCH][libgomp, " Tom de Vries
2022-02-22 14:52 ` Tom de Vries
2021-05-20 9:52 ` [PATCH][libgomp, " Thomas Schwinge
2021-05-20 11:41 ` Tom de Vries [this message]
2021-11-26 12:10 ` *PING* " Tobias Burnus
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=7e88d3c6-b0d5-8356-e20e-c560513fe455@suse.de \
--to=tdevries@suse.de \
--cc=amonakov@ispras.ru \
--cc=ams@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=thomas@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).