Date: Wed, 30 Oct 2002 09:53:30 -0800 From: Juli Mallett <jmallett@FreeBSD.org> To: David O'Brien <obrien@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG Subject: Re: Objective-C threads Message-ID: <20021030095330.A21110@FreeBSD.org> In-Reply-To: <20021030104311.B60023@newton.issci.ca>; from davidc@issci.ca on Wed, Oct 30, 2002 at 10:43:11AM -0700 References: <20021029190941.A43525@newton.issci.ca> <3DBF4C35.B554A7C1@mindspring.com> <20021029211322.B45337@newton.issci.ca> <3DBF8FD8.A68747D8@mindspring.com> <20021030101943.GB80447@dragon.nuxi.com> <20021030092353.D58476@newton.issci.ca> <20021030170916.GA13375@dragon.nuxi.com> <20021030092220.A18067@FreeBSD.org> <20021030104311.B60023@newton.issci.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
* De: Chad David <davidc@issci.ca> [ Data: 2002-10-30 ] [ Subjecte: Re: Objective-C threads ] > On Wed, Oct 30, 2002 at 09:22:21AM -0800, Juli Mallett wrote: > > * De: David O'Brien <obrien@FreeBSD.ORG> [ Data: 2002-10-30 ] > > [ Subjecte: Re: Objective-C threads ] > > > On Wed, Oct 30, 2002 at 09:23:53AM -0700, Chad David wrote: > > > > > > > > Which brings us back to my original question... why are ObjC threads > > > > disabled? I don't much care about my other patches, I just want > > > > to know who the 10 others are who will break if we enable threads, > > > > and how to fix that breakage. My minor patches were only posted because > > > > you asked :). > > > > > > I am not sure. But for some reason you didn't provide a patch that would > > > turn them on. All you provided was a minor patches that really should go > > > thru the offical FSF GCC repo in-route to FreeBSD. So back to my > > > original request. Do you have a patch for changing this part of the way > > > we configure and build ObjC that you feel might be wrong? > > > > With a simple test program, > > > > [cut] > > > > > obj = [Test alloc]; > > [obj set:"Threads"]; > > pthread_create(&td, NULL, thr, NULL); > > This will work the way FreeBSD currently builds ObjC, what I want > to use is objc_thread_xxx() and friends, so that the code maintains > portability, and the runtime is kept up to date with what is going > on. My point was it doesn't break currently working things in a threading case. Your observations of the real issues are, of course, correct :) When you're chattign with the gcc objc people, get them to fix the nit in README.threads or THREADS where it says if you have a thread-aware GCC you can use thr-gcc.c... That file does not seem to exist, at least not in our contrib sources. juli. -- Juli Mallett <jmallett@FreeBSD.org> | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@FreeBSD.org http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021030095330.A21110>