public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] Adjust 'libgomp.c-c++-common/requires-3.c' Date: Thu, 7 Jul 2022 12:08:29 +0000 (GMT) [thread overview] Message-ID: <20220707120829.69A6C3858D32@sourceware.org> (raw) https://gcc.gnu.org/g:f86ab292ecc4e34aaecf2290da521ec39fb2453b commit f86ab292ecc4e34aaecf2290da521ec39fb2453b Author: Thomas Schwinge <thomas@codesourcery.com> Date: Thu Jul 7 14:05:17 2022 +0200 Adjust 'libgomp.c-c++-common/requires-3.c' As documented, this one does "Check diagnostic by device-compiler's lto1". Indeed there are none when compiling with '-foffload=disable' with an offloading-enabled compiler, so we should use 'offload_target_[...]', as used in other similar test cases. Follow-up to recent commit 683f11843974f0bdf42f79cdcbb0c2b43c7b81b0 "OpenMP: Move omp requires checks to libgomp". libgomp/ * testsuite/libgomp.c-c++-common/requires-3.c: Adjust. (cherry picked from commit 99831ceb872cd1a3f3207fd2dfe03ef65dd9089b) Diff: --- libgomp/ChangeLog.omp | 7 +++++++ libgomp/testsuite/libgomp.c-c++-common/requires-3.c | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp index ab3dce72077..8ace421648f 100644 --- a/libgomp/ChangeLog.omp +++ b/libgomp/ChangeLog.omp @@ -1,3 +1,10 @@ +2022-07-07 Tobias Burnus <tobias@codesourcery.com> + + Backport from mainline: + 2022-07-07 Thomas Schwinge <thomas@codesourcery.com> + + * testsuite/libgomp.c-c++-common/requires-3.c: Adjust. + 2022-07-07 Tobias Burnus <tobias@codesourcery.com> Backport from mainline: diff --git a/libgomp/testsuite/libgomp.c-c++-common/requires-3.c b/libgomp/testsuite/libgomp.c-c++-common/requires-3.c index 4b07ffdd09b..7091f400ef0 100644 --- a/libgomp/testsuite/libgomp.c-c++-common/requires-3.c +++ b/libgomp/testsuite/libgomp.c-c++-common/requires-3.c @@ -1,4 +1,4 @@ -/* { dg-do link { target offloading_enabled } } */ +/* { dg-do link { target { offload_target_nvptx || offload_target_amdgcn } } } */ /* { dg-additional-sources requires-3-aux.c } */ /* Check diagnostic by device-compiler's lto1.
reply other threads:[~2022-07-07 12:08 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220707120829.69A6C3858D32@sourceware.org \ --to=burnus@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).