Daniel Latypov 4fdacef8ac kunit: move check if assertion passed into the macros ... Currently the code always calls kunit_do_assertion() even though it does nothing when `pass` is true. This change moves the `if(!(pass))` check into the macro instead and renames the function to kunit_do_failed_assertion(). I feel this a bit easier to read and understand. This has the potential upside of avoiding a function call that does nothing most of the time (assuming your tests are passing) but comes with the downside of generating a bit more code and branches. We try to mitigate the branches by tagging them with `unlikely()`. This also means we don't have to initialize structs that we don't need, which will become a tiny bit more expensive if we switch over to using static variables to try and reduce stack usage. (There's runtime code to check if the variable has been initialized yet or not). Signed-off-by: Daniel Latypov <dlatypov@google.com> Reviewed-by: Brendan Higgins <brendanhiggins@google.com> Reviewed-by: David Gow <davidgow@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>		2022-01-25 12:49:40 -07:00
..
assert.h	kunit: replace kernel.h with the necessary inclusions	2022-01-20 08:52:54 +02:00
test-bug.h	kunit: fix -Wunused-function warning for __kunit_fail_current_test	2021-04-06 15:22:39 -06:00
test.h	kunit: move check if assertion passed into the macros	2022-01-25 12:49:40 -07:00
try-catch.h	kunit: hide unexported try-catch interface in try-catch-impl.h	2020-01-09 16:42:09 -07:00