| commit | 616df135110ccae617ef9f10e0814fa48462cc37 | |
| author | David Howells <dhowells@redhat.com> | |
| Wed, 15 Apr 2009 18:34:51 +0000 (15 19:34 +0100) | ||
| committer | Linus Torvalds <torvalds@linux-foundation.org> | |
| Wed, 15 Apr 2009 20:55:13 +0000 (15 13:55 -0700) | ||
| tree | ddeec495b62e22a5f96cf0d2df85be16709debd3 | treesnapshot (tar.gz zip) |
| parent | 76d320a5072f93abb913e9b9d84304f819c34b96 | commitdiff |
MN10300: Stop gcc from generating uninitialised variable warnings after BUG()
Stop gcc from generating uninitialised variable warnings after BUG(). The
problem is that MN10300's implementation of BUG() invokes system call 15 which
doesn't return - but there's no way to tell the compiler that and also emit the
bug table element with the correct file and line data.
So instead, we make the do...while wrapper in _debug_bug_trap() an endless loop
from which there's no escape.
Also, while we're at it, (1) get rid of _debug_bug_trap() and just implement
directly as BUG(), and (2) make the implementation of BUG() contingent on
CONFIG_BUG=y.
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Stop gcc from generating uninitialised variable warnings after BUG(). The
problem is that MN10300's implementation of BUG() invokes system call 15 which
doesn't return - but there's no way to tell the compiler that and also emit the
bug table element with the correct file and line data.
So instead, we make the do...while wrapper in _debug_bug_trap() an endless loop
from which there's no escape.
Also, while we're at it, (1) get rid of _debug_bug_trap() and just implement
directly as BUG(), and (2) make the implementation of BUG() contingent on
CONFIG_BUG=y.
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
| arch/mn10300/include/asm/bug.h | diffblobblamehistory |