[Top] [All Lists]

Re: Issue with BUG() in asm-gemeric/bug.h if CONFIG_BUG=n

To: Ralf Baechle <>
Subject: Re: Issue with BUG() in asm-gemeric/bug.h if CONFIG_BUG=n
From: David Daney <>
Date: Mon, 30 Sep 2013 08:53:47 -0700
Cc:, Arnd Bergmann <>, David Howells <>, Markos Chandras <>,, Andrew Pinski <>, John Crispin <>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mQtbQng35R0acurKjjeR5qcrWaJLnXPxZWNSAvgMByo=; b=GsvTEO4R2S/0RxTbQbF+ouZc90un3chpurR7HEVicKDfr189KURied8sPU6XYlbyoh LDKEbVkitgj9ArUTZxMzBo8ktXmbwLjDobzqPhZk2V/KFI2Tmrs7Dr+eTJ1RFGoQ50au xlfVFVuMfhq9XJrWwAI2kfQ2ZX0qP93hjEfOLgTWtMbkMKy3s3DuyrKT9ZchI9ebKZS0 yVjaGi3i2k+ft+euTupap2/WZmHQq4oY3m3UO6nY0fnTEEzM4SOqVqikItCvewcMsdoU 5TO8SxdRuFgLFM71BQnZ+GsXjhp4UJWicKMvJlbhfW5Gnbr35B+3k4SCwmqtMKS8qY4f 5QLQ==
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
On 09/30/2013 07:56 AM, Ralf Baechle wrote:
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled.  Here's a test case extracted from one of them:

  * Definition of BUG taken from asm-generic/bug.h for the CONFIG_BUG=n case
#define BUG()   do {} while(0)

int foo(int arg)
        int res;

        if (arg == 1)
                res = 23;
        else if (arg == 2)
                res = 42;

        return res;

[ralf@h7 ~]$ gcc -O2 -Wall -c bug.c
bug.c: In function ‘foo’:
bug.c:17:2: warning: ‘res’ may be used uninitialized in this function 
   return res;

It's fairly obvious to see what's happening here - GCC doesn't know that
the else case can not be reached, thus razorsharply concludes that res
may be used uninitialized.

There several locations where MIPS - possibly other architectures as well -
is affected by this.

I think the definition of BUG should be changed to something like

#define BUG()   unreachable()
unreachable() will depending on the compiler being used, expand either
into a call to __builtin_unreachable() or where that function is
unavailable, into do {} while (1).

The *only* reason we have CONFIG_BUG=n is to reduce code size.

Sticking in that empty loop, negates the entire point.

IMHO: We should do one of:
 o Make CONFIG_BUG=y mandatory
 o Ignore the warnings.
 o Fix the warning sites so they quit Warning.

So I don't think the patch is really an improvement over the status quo.

David Daney

__builtin_unreachable() was introduce for GCC 4.5.0.

This means there'd be minor bloat for antique compilers - but probably
even better code generation for compilers supporting __builtin_unreachable().


Signed-off-by: Ralf Baechle <>

  include/asm-generic/bug.h | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/asm-generic/bug.h b/include/asm-generic/bug.h
index 7d10f96..6f78771 100644
--- a/include/asm-generic/bug.h
+++ b/include/asm-generic/bug.h
@@ -108,7 +108,7 @@ extern void warn_slowpath_null(const char *file, const int 

  #else /* !CONFIG_BUG */
  #ifndef HAVE_ARCH_BUG
-#define BUG() do {} while(0)
+#define BUG() unreachable()

  #ifndef HAVE_ARCH_BUG_ON

----- End forwarded message -----


<Prev in Thread] Current Thread [Next in Thread>