public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Nicolas Koenig <nk@koenigni.com>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch, rfc] Fortran async I/O support
Date: Thu, 24 May 2018 01:30:00 -0000	[thread overview]
Message-ID: <df4cb718-e3a7-b901-bb01-ceca928c8e04@charter.net> (raw)
In-Reply-To: <0dd1ef87-e32e-7cb7-b7d9-2f48da360b56@koenigni.com>

On 05/21/2018 09:05 AM, Nicolas Koenig wrote:
> Hey everyone,
> 
> Thomas and I have been working on adding asynchronous I/O to 
> libgfortran. The patch is almost done, the only thing still missing is 
> to link libgfortran against libpthread if it exists(which is for some 
> reason necessary despite using __gthread) and deactivating it if 
> libpthread doesn't exist (MinGW). At the moment it is still required to 
> explicitly link against libpthread with -pthread when a program is 
> compiled. Because of this we weren't able to run regression tests yet, 
> since every single test fails.
> 
> It would be great if somebody else could try the patch and report their 
> experiences. Also, if anyone knows how to add the whole conditional 
> libpthread thing in the build script, a little help would be very welcome.
> 
>      Nicolas
> 
> P.S.: I have a new email address, the old one has some problems.
> 

I will try to give this a run this weekend.

Jerry

  reply	other threads:[~2018-05-24  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 16:05 Nicolas Koenig
2018-05-24  1:30 ` Jerry DeLisle [this message]
2018-05-30 10:15 Dominique d'Humières

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=df4cb718-e3a7-b901-bb01-ceca928c8e04@charter.net \
    --to=jvdelisle@charter.net \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nk@koenigni.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).