From owner-freebsd-current Thu Aug 16 9:42: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id D0F7737B401 for ; Thu, 16 Aug 2001 09:42:01 -0700 (PDT) (envelope-from mark@whistle.com) Received: from [207.76.207.129] (PBG4.whistle.com [207.76.207.129]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA79152 for ; Thu, 16 Aug 2001 09:41:41 -0700 (PDT) Mime-Version: 1.0 X-Sender: mark-ml@207.76.206.1 Message-Id: In-Reply-To: References: Date: Thu, 16 Aug 2001 09:42:19 -0700 To: current@FreeBSD.ORG From: Mark Peek Subject: Re: Kernel stack hogs list available Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 11:29 AM -0400 8/16/01, Robert Watson wrote: >This is way cool stuff. I assume these are done based on i386 stack frame >layouts? Running on other platforms will result in different alignment >(minor issue, as most of the time it will just be a few bytes here or >there), and some different code (specifically, alpha/, ia64/, etc). >Together with functional cross-compiling, this could be a very useful tool >indeed. Perhaps someone on the alpha side could do the same test run on >that platform? Also, the number of registers and compiler flags such as optimization will cause different register spills to occur. You can't just count up the bytes by looking at the code, it needs to be done in the compiler alongside register allocation. I know we only recommend -O compilations but other flags could affect the count. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message