aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/kunit/try-catch.h
diff options
context:
space:
mode:
authorBrendan Higgins <brendanhiggins@google.com>2019-09-23 02:02:38 -0700
committerShuah Khan <skhan@linuxfoundation.org>2019-09-30 17:35:01 -0600
commit33adf80f5b52e3f7c55ad66ffcaaff93c6888aaa (patch)
tree0fdeb5b24fbd5fd2dcfcf6ae185c7039b5f6fd4a /include/kunit/try-catch.h
parentkunit: test: add initial tests (diff)
downloadwireguard-linux-33adf80f5b52e3f7c55ad66ffcaaff93c6888aaa.tar.xz
wireguard-linux-33adf80f5b52e3f7c55ad66ffcaaff93c6888aaa.zip
objtool: add kunit_try_catch_throw to the noreturn list
Fix the following warning seen on GCC 7.3: kunit/test-test.o: warning: objtool: kunit_test_unsuccessful_try() falls through to next function kunit_test_catch() kunit_try_catch_throw is a function added in the following patch in this series; it allows KUnit, a unit testing framework for the kernel, to bail out of a broken test. As a consequence, it is a new __noreturn function that objtool thinks is broken (as seen above). So fix this warning by adding kunit_try_catch_throw to objtool's noreturn list. Reported-by: kbuild test robot <lkp@intel.com> Signed-off-by: Brendan Higgins <brendanhiggins@google.com> Acked-by: Josh Poimboeuf <jpoimboe@redhat.com> Link: https://www.spinics.net/lists/linux-kbuild/msg21708.html Cc: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'include/kunit/try-catch.h')
0 files changed, 0 insertions, 0 deletions