This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: What's the purpose of __fp_lock_all() / __fp_unlock_all() ?
- From: Yaakov Selkowitz <yselkowitz at cygwin dot com>
- To: newlib at sourceware dot org
- Date: Mon, 19 Jun 2017 17:55:52 -0500
- Subject: Re: What's the purpose of __fp_lock_all() / __fp_unlock_all() ?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=cygwin.com
- Authentication-results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=none smtp.mailfrom=yselkowitz at cygwin dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 87BD0C04B926
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 87BD0C04B926
- References: <1497910479.1511.10.camel@op.pl>
On 2017-06-19 17:14, Freddie Chopin wrote:
What's the purpose of __fp_lock_all() and __fp_unlock_all() from
newlib/libc/stdio/findfp.c? These functions don't seem to be used
anywhere and they have no public prototypes. Could they be just deleted
from the repository?
They are used internally by Cygwin (winsup/cygwin/thread.cc).
--
Yaakov