Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 22 Nov 2002 01:44:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 22 Nov 2002 01:44:00 -0500 Received: from air-2.osdl.org ([65.172.181.6]:30694 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id ; Fri, 22 Nov 2002 01:43:59 -0500 Date: Thu, 21 Nov 2002 22:49:23 -0800 (PST) From: "Randy.Dunlap" X-X-Sender: To: Roland Dreier cc: dan carpenter , , , Subject: Re: [LIST] large local declarations In-Reply-To: <87vg2q15q5.fsf@love-shack.home.digitalvampire.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 946 Lines: 27 On 21 Nov 2002, Roland Dreier wrote: | >>>>> "dan" == dan carpenter writes: | | dan> I have a smatch script (smatch.sf.net) that finds the the | dan> size of local variables. I created an allyesconfig with | dan> 2.5.48 and tested it. These were the functions that declared | dan> local datas with size of 5 digits or more (in bits). | | This is a minor complaint, but... why do you report the data sizes in | bits? I find myself forced to mentally divide every size by 8. Every | variable (obviously) has a size that's a whole number of bytes. Why | not just report bytes? I second that. It's not just Roland... But thanks for doing it anyway. -- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/