From: Tobias Burnus <tobias@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>, Tom de Vries <tdevries@suse.de>
Cc: <gcc-patches@gcc.gnu.org>, Thomas Schwinge <thomas@schwinge.name>
Subject: Re: [PATCH][libgomp, testsuite] Scale down some OpenACC test-cases
Date: Fri, 25 Mar 2022 11:04:06 +0100 [thread overview]
Message-ID: <40a25c58-630f-d36c-06e5-6ea0769d53ec@codesourcery.com> (raw)
In-Reply-To: <Yj2K5xjnoW7Zduch@tucnak>
On 25.03.22 10:27, Jakub Jelinek via Gcc-patches wrote:
> On Fri, Mar 25, 2022 at 10:18:49AM +0100, Tom de Vries wrote:
>> [...]
>> Fix this by scaling down the failing test-cases.
>> Tested on x86_64-linux with nvptx accelerator.
>> [...]
> Will defer to Thomas, as it is a purely OpenACC change.
>
> One way to do it is
> /* { dg-additional-options "-DEXPENSIVE" { target run_expensive_tests } } */
> and using
> #ifdef EXPENSIVE
> [...]
>
> For the Fortran test it would mean .F90 extension though...
Alternative, use the "-cpp" flag in 'dg-additional-options', which also
enables the C-pre-processor pre-processing in gfortran.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2022-03-25 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 9:18 Tom de Vries
2022-03-25 9:27 ` Jakub Jelinek
2022-03-25 10:04 ` Tobias Burnus [this message]
2022-03-25 12:08 ` Tom de Vries
2022-03-25 12:12 ` Jakub Jelinek
2022-03-25 12:35 ` Thomas Schwinge
2022-03-25 12:54 ` 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=40a25c58-630f-d36c-06e5-6ea0769d53ec@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).