public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
	koenigni <koenigni@student.ethz.ch>
Subject: Re: PTHREAD_MUTEX_SHARED on Cygwin
Date: Sun, 10 Jan 2021 20:40:38 +0100	[thread overview]
Message-ID: <04ee15cb-21d4-c198-b690-bbf1f0d21982@netcologne.de> (raw)
In-Reply-To: <657c8576-2715-8c80-a59a-23453306230f@netcologne.de>

I wrote:

>> Is it correct that PTHREAD_PROCESS_SHARED is not supported on
>> Cygwin?  Is it supported for condition variables, or is the fact
>> that it is reported as working an oversight?

First, thanks for the replies. I'll give sort of a compound answer.

Brian Inglis wrote:

 >> The function is supported but that parameter is not implemented or
 >> tested and returns EINVAL:

> If PTHREAD_PROCESS_SHARED does not work, are there known workarounds?

 > If you have the ability and time to work on this, one of the Cygwin
 > developers/maintainers may be able to assist.

Unfortunately, I have neither.  What I know about Cygwin is from a pure
user perspective, and what time I can deveote is soaked up by gfortran
in general and (currently) by the shared coarray branch in particular.

And in another mail:

 > It looks like there was nothing on this between implementation circ
 > 2002 and:

 > https://sourceware.org/pipermail/cygwin/2019-February/240178.html

That suggests it is not somthing trivially done, unfortunately.

 > Presumably your goal is to support or disqualify gfortran coarrays:

To be (a bit) pedantic, gfortran currently supports OpenCoarrays
(via -fcoarray=lib) for which you also need MPI. Not sure what
the status on Cygwin is for those.

My enquiry is about another implementation, which is based on
shared memory and on processes.

 > https://gcc.gnu.org/pipermail/fortran/2021-January/055542.html

The goal would be to support, of course, but this will not work
on current Cygwin.  Using SysV IPC or Windows directly could be
a solution, but at the moment the focus is on implementing the
many still missing features. The code is modular enough that
a drop-in solution for systems which do not support PTHTEAD_MUTEX_SHARED
can be added later without too much hassle.

Thanks for your pointers!

Best regards

	Thomas

      parent reply	other threads:[~2021-01-10 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 18:23 Thomas Koenig
2021-01-09 19:58 ` Brian Inglis
2021-01-09 22:16   ` PTHREAD_PROCESS_SHARED not implemented (was PTHREAD_MUTEX_SHARED on Cygwin) Brian Inglis
2021-01-09 22:54     ` Brian Inglis
2021-01-11  7:01     ` Noel Grandin
2021-01-09 20:24 ` PTHREAD_MUTEX_SHARED on Cygwin Marco Atzeri
2021-01-10 19:40 ` Thomas Koenig [this message]

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=04ee15cb-21d4-c198-b690-bbf1f0d21982@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=cygwin@cygwin.com \
    --cc=koenigni@student.ethz.ch \
    /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).