From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Patch] Add libgomp.fortran/order-reproducible-*.f90 [Re: [committed] openmp: Differentiate between order(concurrent) and order(reproducible:concurrent)]
Date: Fri, 1 Oct 2021 11:45:53 +0200 [thread overview]
Message-ID: <20211001094553.GK304296@tucnak> (raw)
In-Reply-To: <93c9d8dc-aa2d-b5f8-b201-fd8ac69544a5@codesourcery.com>
On Fri, Oct 01, 2021 at 11:34:15AM +0200, Tobias Burnus wrote:
> On 01.10.21 11:03, Jakub Jelinek wrote:
> > 2021-10-01 Jakub Jelinek <jakub@redhat.com>
> > libgomp/
> > * testsuite/libgomp.c-c++-common/order-reproducible-1.c: New test.
> > * testsuite/libgomp.c-c++-common/order-reproducible-2.c: New test.
>
> Attached is the Fortran version of the two patches – the Fortran FE
> modifications were already in Jakub's patch.
>
> 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
> Add libgomp.fortran/order-reproducible-*.f90
>
> libgomp/ChangeLog:
>
> * testsuite/libgomp.fortran/order-reproducible-1.f90: New test
> based on libgomp.c-c++-common/order-reproducible-1.c.
> * testsuite/libgomp.fortran/order-reproducible-2.f90: Likewise.
>
> .../libgomp.fortran/order-reproducible-1.f90 | 70 ++++++++++++++++++++++
> .../libgomp.fortran/order-reproducible-2.f90 | 36 +++++++++++
> 2 files changed, 106 insertions(+)
>
> diff --git a/libgomp/testsuite/libgomp.fortran/order-reproducible-1.f90 b/libgomp/testsuite/libgomp.fortran/order-reproducible-1.f90
> new file mode 100644
> index 00000000000..2b852ebc70b
> --- /dev/null
> +++ b/libgomp/testsuite/libgomp.fortran/order-reproducible-1.f90
> @@ -0,0 +1,70 @@
No
! { dg-additional-sources my-usleep.c }
here? How does it work then?
And no my-usleep.c in the patch.
> +program main
> + implicit none
> + interface
> + subroutine usleep(t) bind(C, name="my_usleep")
> + use iso_c_binding
> + integer(c_int), value :: t
> + end subroutine
> + end interface
> --- /dev/null
> +++ b/libgomp/testsuite/libgomp.fortran/order-reproducible-2.f90
> @@ -0,0 +1,36 @@
> +! { dg-additional-sources my-usleep.c }
> +program main
> + implicit none
> + interface
> + subroutine usleep(t) bind(C, name="my_usleep")
> + use iso_c_binding
> + integer(c_int), value :: t
> + end subroutine
> + end interface
Jakub
next prev parent reply other threads:[~2021-10-01 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 9:03 [committed] openmp: Differentiate between order(concurrent) and order(reproducible:concurrent) Jakub Jelinek
2021-10-01 9:34 ` [Patch] Add libgomp.fortran/order-reproducible-*.f90 [Re: [committed] openmp: Differentiate between order(concurrent) and order(reproducible:concurrent)] Tobias Burnus
2021-10-01 9:45 ` Jakub Jelinek [this message]
2021-10-02 7:52 ` Tobias Burnus
2021-10-02 8:16 ` Jakub Jelinek
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=20211001094553.GK304296@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@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).