From owner-freebsd-hackers Mon Oct 29 16:57: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id 33D5D37B409 for ; Mon, 29 Oct 2001 16:56:59 -0800 (PST) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id 7A00F62D01; Mon, 29 Oct 2001 16:56:58 -0800 (PST) Date: Mon, 29 Oct 2001 16:57:08 -0800 (PST) From: Lamont Granquist To: Daniel Eischen Cc: Subject: Re: MT-Safe wrapper around memcpy()? In-Reply-To: Message-ID: <20011029165510.K35607-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks! Precisely what I was looking for. I coded up the routines today and they seem to work fine. On Mon, 29 Oct 2001, Daniel Eischen wrote: > The _THREAD_SAFE macro has gone away anyways (in -current), and we > (FreeBSD) shouldn't be conditionally compiling code in libc dependent > on whether libc_r is being built or not. And I wouldn't recommend it > for user libraries either. > > Take a look at how libgcc works (src/contrib/gcc.295/gthr-posix.h). [...snip...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message