From owner-freebsd-current Mon Jul 12 23:21:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ducky.net (gate.ducky.net [199.2.211.252]) by hub.freebsd.org (Postfix) with ESMTP id 7256D14BD0 for ; Mon, 12 Jul 1999 23:21:44 -0700 (PDT) (envelope-from mike@ducky.net) Received: from ducky.net (localhost.ducky.net [127.0.0.1]) by ducky.net (8.9.1/8.8.5) with ESMTP id XAA18700; Mon, 12 Jul 1999 23:11:54 -0700 (PDT) Message-Id: <199907130611.XAA18700@ducky.net> To: Mike Haertel Cc: Mike Smith , Matthew Dillon , Luoqi Chen , dfr@nlsystems.com, jeremyp@gsmx07.alcatel.com.au, freebsd-current@FreeBSD.ORG, mike@ducky.net Subject: Re: "objtrm" problem probably found (was Re: Stuck in "objtrm") In-reply-to: Your message of "Mon, 12 Jul 1999 23:09:19 PDT." <199907130609.XAA18672@ducky.net> Date: Mon, 12 Jul 1999 23:11:54 -0700 From: Mike Haertel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Second answer: in the real world, we're nearly always hitting the >cache on stack operations associated with calls and argument passing, >but not less often on operations in the procedure body. So, in ^^^ typo Urk. I meant to say "less often", delete the "not". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message