From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw01.freescale.net (az33egw01.freescale.net [192.88.158.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw01.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id A878CDE0A6 for ; Fri, 12 Oct 2007 05:56:06 +1000 (EST) Date: Thu, 11 Oct 2007 14:55:44 -0500 From: Scott Wood To: Olof Johansson Subject: Re: [PATCH 2/2] powerpc: Switch to generic WARN_ON()/BUG_ON() Message-ID: <20071011195544.GA4247@loki.buserror.net> References: <20071011171211.GB10877@lixom.net> <20071011171413.GC10877@lixom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20071011171413.GC10877@lixom.net> Cc: grundler@parisc-linux.org, linux-kernel@vger.kernel.org, kyle@parisc-linux.org, linuxppc-dev@ozlabs.org, lethal@linux-sh.org, akpm@linux-foundation.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Oct 11, 2007 at 12:14:13PM -0500, Olof Johansson wrote: > Not using the ppc-specific WARN_ON/BUG_ON constructs actually saves about > 4K text on a ppc64_defconfig. The main reason seems to be that prepping > the arguments to the conditional trap instructions is more work than > just doing a compare and branch. It'd be nice if we could get GCC to generate bug table entries for __builtin_trap(); that way we could use GCC's ability to put arbitrary conditions in the trap instruction. -Scott