From owner-freebsd-current Mon Jul 12 23: 2:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 87F3E14BD0 for ; Mon, 12 Jul 1999 23:02:40 -0700 (PDT) (envelope-from a.reilly@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA03028 for ; Tue, 13 Jul 1999 16:00:07 +1000 (EST) X-BPC-Relay-Envelope-From: a.reilly@lake.com.au X-BPC-Relay-Envelope-To: X-BPC-Relay-Sender-Host: m5.c2.telstra-mm.net.au [24.192.3.20] X-BPC-Relay-Info: Message delivered directly. Received: from areilly.bpc-users.org (CPE-24-192-48-172.nsw.bigpond.net.au [24.192.48.172]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id QAA01623 for ; Tue, 13 Jul 1999 16:00:05 +1000 (EST) Received: (qmail 94686 invoked by uid 1000); 13 Jul 1999 06:00:05 -0000 From: "Andrew Reilly" Date: Tue, 13 Jul 1999 16:00:05 +1000 To: Mike Smith Cc: Andrew Reilly , Mike Haertel , Matthew Dillon , Luoqi Chen , dfr@nlsystems.com, jeremyp@gsmx07.alcatel.com.au, freebsd-current@FreeBSD.ORG Subject: Re: "objtrm" problem probably found (was Re: Stuck in "objtrm") Message-ID: <19990713160005.B94421@gurney.reilly.home> References: <19990713153716.A94421@gurney.reilly.home> <199907130538.WAA04527@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907130538.WAA04527@dingo.cdrom.com>; from Mike Smith on Mon, Jul 12, 1999 at 10:38:03PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 12, 1999 at 10:38:03PM -0700, Mike Smith wrote: > I said: > > than indirect function calls on some architectures: inline > > branched code. So you still have a global variable selecting > > locked/non-locked, but it's a boolean, rather than a pointer. > > Your atomic macros are then { if (atomic_lock) asm("lock;foo"); > > else asm ("foo"); } > > This requires you to have all the methods present at compile time, > which defeats the entire purpose of dynamic method loading. Pardon? I didn't see a discussion of dynamic loading anywhere here. We were referring to tiny inlined assembly language routines. The existing implementation is #defines in a C header file. (No, SmallEiffel doesn't do dynamic loading, and that's a perfectly fair and reasonable choice for a large number of applications.) -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message