public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] 'gfortran.dg/gomp/allocate-4.f90' -> 'libgomp.fortran/allocate-5.f90' Date: Thu, 9 Feb 2023 11:34:38 +0000 (GMT) [thread overview] Message-ID: <20230209113438.5D1B63858C50@sourceware.org> (raw) https://gcc.gnu.org/g:7e1963a4e6ac97b6629c1e9e858ae28487f518cf commit 7e1963a4e6ac97b6629c1e9e858ae28487f518cf Author: Thomas Schwinge <thomas@codesourcery.com> Date: Mon Jan 30 18:04:16 2023 +0100 'gfortran.dg/gomp/allocate-4.f90' -> 'libgomp.fortran/allocate-5.f90' Otherwise, for build-tree testing: [...]/gcc/testsuite/gfortran.dg/gomp/allocate-4.f90:10:7: Fatal Error: Cannot open module file 'omp_lib.mod' for reading at (1): No such file or directory ..., and thus corresponding FAILs. (Not renamed to 'libgomp.fortran/allocate-4.f90', as that one already exists.) Fix-up for og12 commit 491478d12b83e102f72858e8a871a25c951df293 "Add parsing support for allocate directive (OpenMP 5.0)". gcc/testsuite/ * gfortran.dg/gomp/allocate-4.f90: Cut. libgomp/ * testsuite/libgomp.fortran/allocate-5.f90: Paste. Diff: --- gcc/testsuite/ChangeLog.omp | 2 ++ libgomp/ChangeLog.omp | 2 ++ .../allocate-4.f90 => libgomp/testsuite/libgomp.fortran/allocate-5.f90 | 0 3 files changed, 4 insertions(+) diff --git a/gcc/testsuite/ChangeLog.omp b/gcc/testsuite/ChangeLog.omp index 936e7af0945..f0c58e4d26a 100644 --- a/gcc/testsuite/ChangeLog.omp +++ b/gcc/testsuite/ChangeLog.omp @@ -1,5 +1,7 @@ 2023-02-09 Thomas Schwinge <thomas@codesourcery.com> + * gfortran.dg/gomp/allocate-4.f90: Cut. + * c-c++-common/gomp/uses_allocators-1.c: Cut. * c-c++-common/gomp/uses_allocators-2.c: Likewise. * c-c++-common/gomp/uses_allocators-3.c: Likewise. diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp index 0a3d53602da..603a17e4c8d 100644 --- a/libgomp/ChangeLog.omp +++ b/libgomp/ChangeLog.omp @@ -1,5 +1,7 @@ 2023-02-09 Thomas Schwinge <thomas@codesourcery.com> + * testsuite/libgomp.fortran/allocate-5.f90: Paste. + * testsuite/libgomp.c++/c++.exp (check_effective_target_c) (check_effective_target_c++): New. * testsuite/libgomp.c/c.exp (check_effective_target_c) diff --git a/gcc/testsuite/gfortran.dg/gomp/allocate-4.f90 b/libgomp/testsuite/libgomp.fortran/allocate-5.f90 similarity index 100% rename from gcc/testsuite/gfortran.dg/gomp/allocate-4.f90 rename to libgomp/testsuite/libgomp.fortran/allocate-5.f90
reply other threads:[~2023-02-09 11:34 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=20230209113438.5D1B63858C50@sourceware.org \ --to=tschwinge@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).