public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
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 14:21:00 -0000	[thread overview]
Message-ID: <yddpnzo60lx.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <f5e00468-5373-5ffd-67f1-0f197eb1659e@netcologne.de> (Thomas	Koenig's message of "Sun, 15 Jul 2018 13:19:35 +0200")

Hi Thomas,

>> I am currently testing the patch at
>> https://gcc.gnu.org/ml/fortran/2018-07/msg00008.html
>>
>> so far, so good!
>
>> IMO the tests should go to gfortran.dg (they pass my tests).
>
> I put the asycn_io_*.f90 tests into libgomp.fortran because,
> under Linux, gfortran.dg does not link in pthreads, so the
> tests would not be executed in parallel, and some of them
> would fail.
>
> So, here is the final version. I would really like to get this
> into trunk, and out of the way, so Nicolas and I can focus on
> other things.

I've now regtested the patch on i386-pc-solaris2.11 and
sparc-sun-solaris2.11: no regressions and the new tests all PASS.

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?

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2018-07-15 14:21 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 [this message]
2018-07-15 14:52     ` Thomas Koenig
2018-07-15 17:49       ` Rainer Orth
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=yddpnzo60lx.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).