From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "Dominique d'Humières" <dominiq@lps.ens.fr>,
"Nicolas Koenig" <nk@koenigni.com>,
gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Asynchronous I/O, take 3
Date: Sun, 15 Jul 2018 17:49:00 -0000 [thread overview]
Message-ID: <yddlgac5r22.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <c3346520-9d68-f284-a5e4-3b5437409c8c@netcologne.de> (Thomas Koenig's message of "Sun, 15 Jul 2018 16:52:20 +0200")
Hi Thomas,
>> However, I still don't understand why you insist on the hack with
>> putting the async_io_*.f90 tests into the libgomp testsuite. Why not
>> just make the pthread requirement explicit with
>>
>> { dg-require-effective-target pthread }
>> { dg-additional-options "-pthread" }
>>
>> and put them in gfortran.dg where they belong?
>
> Because this does not appear to work with Linux. I, like
> most gfortran developers, work on Linux, and I would like to
> catch any failure during regression-testing on my own system,
> if possible.
huh, what doesn't work? I've just finished an x86_64-pc-linux-gnu
bootstrap with your patch included, added the above to the
async_io_?.f90 tests, linked them to gfortran.dg and ran the tests there
(both 32 and 64-bit multilibs), all PASSed and I verified that they were
linked with -lpthread.
> We have had this discussion with Jakub, and he advised
> us to put all the stuff requiring pthreads into libgomp.
Do you have a pointer to that previous discussion?
> It is debatable if this is a good thing, or if we should
> at least make one round of tests with -pthread enabled.
> However, this is something for the future, and requires knowledge
> of dejagnu that I don't currently have :-)
First of all, we need to see and understand the failure mode, if any.
Making this work with the testsuite is a secondary matter only, and I
can certainly help with that if necessary.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2018-07-15 17:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 13:43 Dominique d'Humières
2018-07-15 11:19 ` Thomas Koenig
2018-07-15 14:21 ` Rainer Orth
2018-07-15 14:52 ` Thomas Koenig
2018-07-15 17:49 ` Rainer Orth [this message]
2018-07-15 17:55 ` Jerry DeLisle
2018-07-15 18:46 ` Rainer Orth
2018-07-15 19:10 ` Jerry DeLisle
2018-07-15 19:36 ` Rainer Orth
2018-07-16 11:25 ` Dominique d'Humières
2018-07-15 19:46 ` Thomas Koenig
2018-07-15 17:53 ` Jerry DeLisle
2018-07-15 17:37 ` Jerry DeLisle
2018-09-02 22:39 ` Bernhard Reutner-Fischer
2018-09-03 9:07 ` Janne Blomqvist
2018-09-03 11:49 ` Bernhard Reutner-Fischer
-- strict thread matches above, loose matches on Subject: below --
2018-07-02 22:17 Thomas König
2018-07-03 14:24 ` Rainer Orth
2018-07-03 14:42 ` Rainer Orth
2018-07-03 17:45 ` Thomas König
2018-07-04 8:04 ` Rainer Orth
2018-07-04 17:17 ` Thomas Koenig
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=yddlgac5r22.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nk@koenigni.com \
--cc=tkoenig@netcologne.de \
/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).