Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 19 Mar 2001 12:50:46 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: pthreads Message-ID: <20010319125046.E18807@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <011c01c0b070$9f8ae6c0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <011c01c0b070$9f8ae6c0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Mon, Mar 19, 2001 at 11:32:09PM +1100 On Mon, Mar 19, 2001 at 11:32:09PM +1100, Robert Collins wrote: >Any objections if I do a little bit of >housekeeping in pthread.h thread.cc & thread.h ? There's a few serious >issues there with the type definitions (which I blindly followed for >pthread_cond* - making it worse :[). No objections to cleanup at all. I've never really liked this code. >I believe I can make it leaner and meaner, and more compatible/easy to >build on in future.... > >Fortunately I believe this can be done without breaking existing >compiled programs (I'll especially test for this). > >As a side effect it will make some of it 64 bit clean. > >Rob > >* and rewrite the guts of thread.cc & thread.h to allocate new objects >on the stack and store the pointer rather than an index. This also >removes the overhead of walking the list for user space requests, and >simplifies the code. How can you allocate things on the stack? That doesn't seem possible. Do you mean the heap? cgf