From: Jakub Jelinek <jakub@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gcc-patches@gcc.gnu.org, Thomas Schwinge <thomas@schwinge.name>
Subject: Re: [PATCH][libgomp, testsuite, nvptx] Limit recursion in declare_target-{1,2}.f90
Date: Fri, 1 Apr 2022 13:26:31 +0200 [thread overview]
Message-ID: <YkbhZ4xvnnIymjZj@tucnak> (raw)
In-Reply-To: <20220401112438.GA19247@delia>
On Fri, Apr 01, 2022 at 01:24:40PM +0200, Tom de Vries wrote:
> Hi,
>
> When running testcases libgomp.fortran/examples-4/declare_target-{1,2}.f90 on
> an RTX A2000 (sm_86) with driver 510.60.02 and with GOMP_NVPTX_JIT=-O0 I run
> into:
> ...
> FAIL: libgomp.fortran/examples-4/declare_target-1.f90 -O0 \
> -DGOMP_NVPTX_JIT=-O0 execution test
> FAIL: libgomp.fortran/examples-4/declare_target-2.f90 -O0 \
> -DGOMP_NVPTX_JIT=-O0 execution test
> ...
>
> Fix this by further limiting recursion depth in the test-cases for nvptx.
>
> Furthermore, make the recursion depth limiting nvptx-specific.
>
> Tested on x86_64 with nvptx accelerator.
>
> Any comments?
>
> Thanks,
> - Tom
>
> [libgomp, testsuite, nvptx] Limit recursion in declare_target-{1,2}.f90
>
> libgomp/ChangeLog:
>
> 2022-04-01 Tom de Vries <tdevries@suse.de>
>
> * testsuite/libgomp.fortran/examples-4/declare_target-1.f90: Define
> and use REC_DEPTH.
> * testsuite/libgomp.fortran/examples-4/declare_target-2.f90: Same.
Ok.
Jakub
next prev parent reply other threads:[~2022-04-01 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 11:24 Tom de Vries
2022-04-01 11:26 ` Jakub Jelinek [this message]
2022-04-01 12:28 ` Thomas Schwinge
2022-04-01 15:34 ` Tom de Vries
2022-04-01 15:38 ` Jakub Jelinek
2022-04-01 15:57 ` Tom de Vries
2022-04-04 11:05 ` Tom de Vries
2022-04-04 11:07 ` Jakub Jelinek
2022-04-04 11:37 ` Tom de Vries
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=YkbhZ4xvnnIymjZj@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tdevries@suse.de \
--cc=thomas@schwinge.name \
/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).