From mboxrd@z Thu Jan 1 00:00:00 1970 From: DM Subject: Re: [PATCH 0/2] Stop some of the abuse of BUG() where compile time checks should be used. Date: Tue, 22 Nov 2011 09:42:40 +0100 Message-ID: <4ECB6080.7050407@gmail.com> References: <1321925466-11280-1-git-send-email-ddaney.cavm@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-bw0-f46.google.com ([209.85.214.46]:63637 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750851Ab1KVImp (ORCPT ); Tue, 22 Nov 2011 03:42:45 -0500 In-Reply-To: <1321925466-11280-1-git-send-email-ddaney.cavm@gmail.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: David Daney Cc: ralf@linux-mips.org, Linus Torvalds , Andrew Morton , David Rientjes , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, David Daney On 2011-11-22 02:31, David Daney wrote: > From: David Daney > > After some, perhaps justified, reluctance to merge dummy symbol > definitions containing BUG() into header files, I propose these patches > instead. > > We define a new compile time assertion BUILD_BUG_ON_USED() that can be > used in places were we expect the compiler's dead code elimination to > get rid of code. This happens mostly in code dealing with huge pages, > but in other places as well. > > The first patch adds BUILD_BUG_ON_USED(), the second gets rid of one > of the main abusers of BUG(). > Perhaps BUILD_BUG() is a more consistent name for this? We would then have BUG() and BUG_ON(x) for run-time vs BUILD_BUG() and BUILD_BUG_ON(x) for compile-time. /DM