From: Tom de Vries <tdevries@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][libgomp, testsuite, nvptx] Limit recursion in declare_target-{1,2}.f90
Date: Mon, 4 Apr 2022 13:37:52 +0200 [thread overview]
Message-ID: <ce11f0bd-9342-2252-24e2-75396198be03@suse.de> (raw)
In-Reply-To: <YkrRh7irMk1L57Sa@tucnak>
On 4/4/22 13:07, Jakub Jelinek wrote:
> On Mon, Apr 04, 2022 at 01:05:12PM +0200, Tom de Vries wrote:
>> 2022-04-04 Tom de Vries <tdevries@suse.de>
>>
>> * testsuite/libgomp.fortran/examples-4/on_device_arch.c: Copy from
>> parent dir.
>
> Wouldn't just ! { dg-additional-sources ../on_device_arch.c }
> work?
I does, pushed with that update.
Thanks,
- Tom
prev parent reply other threads:[~2022-04-04 11:37 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
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 [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=ce11f0bd-9342-2252-24e2-75396198be03@suse.de \
--to=tdevries@suse.de \
--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).