X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D5AC63857808 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1610307646; bh=t03kd1S00gtS0cXsmVuFL/FEFRHZwNzTVxaeEEWVdYU=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=jxfJGwjN0Osa1LZaxK3j93XcX+YAPj9r17OiqYkSxsY7HPY1gnj/AqJzL+gzFDdFr 7992CxiEgcvlX6vb5PXTW6E7JQgntshRC3uE7JUFuzAVx79vZ7h6sFQvQL2db+6NCY XbX9lWs1RWIWEV42mKTj/y4yJf3u+VIho0plg/tI= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7971E385800A Subject: Re: PTHREAD_MUTEX_SHARED on Cygwin To: "cygwin AT cygwin DOT com" , koenigni References: <657c8576-2715-8c80-a59a-23453306230f AT netcologne DOT de> Message-ID: <04ee15cb-21d4-c198-b690-bbf1f0d21982@netcologne.de> Date: Sun, 10 Jan 2021 20:40:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <657c8576-2715-8c80-a59a-23453306230f@netcologne.de> Content-Language: de-DE X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Thomas Koenig via Cygwin Reply-To: Thomas Koenig Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 10AJfDa8022227 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple