From owner-freebsd-arch Wed Nov 29 10:11:58 2000 Delivered-To: freebsd-arch@freebsd.org Received: from net2.gendyn.com (nat2.gendyn.com [204.60.171.12]) by hub.freebsd.org (Postfix) with ESMTP id 2158F37B400 for ; Wed, 29 Nov 2000 10:11:55 -0800 (PST) Received: from [153.11.11.3] (helo=plunger.gdeb.com) by net2.gendyn.com with esmtp (Exim 2.12 #1) id 141Bhn-0002rX-00 for arch@freebsd.org; Wed, 29 Nov 2000 13:11:43 -0500 Received: from orion.caen.gdeb.com ([153.11.109.11]) by plunger.gdeb.com with ESMTP id NAA01053 for ; Wed, 29 Nov 2000 13:08:23 -0500 (EST) Received: from vigrid.com (gpz.clc.gdeb.com [192.168.3.12]) by orion.caen.gdeb.com (8.9.3/8.9.3) with ESMTP id NAA03358 for ; Wed, 29 Nov 2000 13:08:35 -0500 (EST) (envelope-from eischen@vigrid.com) Message-ID: <3A254710.ED8B2C26@vigrid.com> Date: Wed, 29 Nov 2000 13:12:32 -0500 From: Dan Eischen X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: arch@freebsd.org Subject: Modifying FILE to add lock Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any objection to modifying struct __sFILE in stdio.h to add a lock. I am think we need to do this for libpthread. This should let us eliminate the _THREAD_SAFE macro. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message