[PATCH, re-send] Always trap on BUG()
H. Peter Anvin
hpa at zytor.com
Mon Jul 15 18:35:16 EDT 2013
On 07/15/2013 03:27 PM, Russell King - ARM Linux wrote:
> On Mon, Jul 15, 2013 at 03:16:12PM -0700, Andrew Morton wrote:
>> I've been thinking for a while that CONFIG_BUG=n is a pretty dumb thing
>> to do, and that maintaining it (and trying to fix the warnings it
>> produces) aren't worth the effort and that we should remove the whole
>> thing. Perhaps your patch changes that calculus, dunno. Please discuss.
> This isn't about introducing "CONFIG_BUG=n" - this is about making a
> kernel with CONFIG_BUG=n build without producing tonnes and tonnes of
> warnings, as it does today. It makes building randconfig pretty
> useless to find what could be more important warnings.
Well, there are three alternatives here, right:
1. We can use unreachable(), which means that the compiler can assume it
2. We can trap without metadata.
3. We can trap with metadata (current CONFIG_BUG=y).
I am *guessing* this does 2, but it isn't clear.
More information about the linux-arm-kernel