]> git.ipfire.org Git - thirdparty/glibc.git/commit
Fix implicit-fallthrough warnings in tst-setjmp.c.
authorJoseph Myers <joseph@codesourcery.com>
Fri, 15 Feb 2019 13:44:17 +0000 (13:44 +0000)
committerJoseph Myers <joseph@codesourcery.com>
Fri, 15 Feb 2019 13:44:17 +0000 (13:44 +0000)
commit365f05c7a5f16aaaec06465ab6c89247c66b4574
tree934f1d62a27b826a052aa84755683cb226127014
parent56a731d4ad319e473851893980e734b7ee42c1a0
Fix implicit-fallthrough warnings in tst-setjmp.c.

Building the testsuite with -Wextra (together with
-Wno-cast-function-type -Wno-clobbered -Wno-expansion-to-defined
-Wno-missing-field-initializers -Wno-old-style-declaration
-Wno-shift-negative-value -Wno-sign-compare -Wno-type-limits
-Wno-unused-parameter, which reflect the set of -Wextra warnings for
which glibc itself is not currently clean on x86_64) showed up
implicit-fallthrough warnings in tst-setjmp.c.  Those warnings appear
to be false positives, arising from a function "jump" that calls
longjmp not itself being marked as noreturn; thus, this patch adds the
noreturn marking to that function to fix the warnings.

Tested for x86_64.

* setjmp/tst-setjmp.c (jump): Use __attribute__ ((__noreturn__)).
ChangeLog
setjmp/tst-setjmp.c