2022-04-28 09:24:11 -07:00
|
|
|
// SPDX-FileCopyrightText: 2013 Dolphin Emulator Project
|
|
|
|
// SPDX-FileCopyrightText: 2014 Citra Emulator Project
|
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
2015-01-20 17:16:47 -08:00
|
|
|
|
|
|
|
#pragma once
|
|
|
|
|
2015-05-11 22:52:31 -07:00
|
|
|
#include "common/logging/log.h"
|
2015-01-20 17:16:47 -08:00
|
|
|
|
2021-04-01 23:43:26 -07:00
|
|
|
// Sometimes we want to try to continue even after hitting an assert.
|
|
|
|
// However touching this file yields a global recompilation as this header is included almost
|
|
|
|
// everywhere. So let's just move the handling of the failed assert to a single cpp file.
|
|
|
|
void assert_handle_failure();
|
|
|
|
|
2015-02-17 20:06:48 -08:00
|
|
|
// For asserts we'd like to keep all the junk executed when an assert happens away from the
|
|
|
|
// important code in the function. One way of doing this is to put all the relevant code inside a
|
|
|
|
// lambda and force the compiler to not inline it. Unfortunately, MSVC seems to have no syntax to
|
|
|
|
// specify __declspec on lambda functions, so what we do instead is define a noinline wrapper
|
|
|
|
// template that calls the lambda. This seems to generate an extra instruction at the call-site
|
|
|
|
// compared to the ideal implementation (which wouldn't support ASSERT_MSG parameters), but is good
|
|
|
|
// enough for our purposes.
|
|
|
|
template <typename Fn>
|
|
|
|
#if defined(_MSC_VER)
|
2021-04-01 23:43:26 -07:00
|
|
|
[[msvc::noinline]]
|
2015-02-17 20:06:48 -08:00
|
|
|
#elif defined(__GNUC__)
|
2021-04-01 23:43:26 -07:00
|
|
|
[[gnu::cold, gnu::noinline]]
|
2015-02-17 20:06:48 -08:00
|
|
|
#endif
|
2020-08-24 01:06:18 -07:00
|
|
|
static void
|
|
|
|
assert_noinline_call(const Fn& fn) {
|
2015-02-17 20:06:48 -08:00
|
|
|
fn();
|
2021-04-01 23:43:26 -07:00
|
|
|
assert_handle_failure();
|
2015-02-17 20:06:48 -08:00
|
|
|
}
|
|
|
|
|
2016-09-17 17:38:01 -07:00
|
|
|
#define ASSERT(_a_) \
|
|
|
|
do \
|
|
|
|
if (!(_a_)) { \
|
2018-07-02 09:20:50 -07:00
|
|
|
assert_noinline_call([] { LOG_CRITICAL(Debug, "Assertion Failed!"); }); \
|
2016-09-17 17:38:01 -07:00
|
|
|
} \
|
|
|
|
while (0)
|
|
|
|
|
|
|
|
#define ASSERT_MSG(_a_, ...) \
|
|
|
|
do \
|
|
|
|
if (!(_a_)) { \
|
2018-07-02 09:20:50 -07:00
|
|
|
assert_noinline_call([&] { LOG_CRITICAL(Debug, "Assertion Failed!\n" __VA_ARGS__); }); \
|
2016-09-17 17:38:01 -07:00
|
|
|
} \
|
|
|
|
while (0)
|
2015-01-20 17:16:47 -08:00
|
|
|
|
2019-10-05 07:45:01 -07:00
|
|
|
#define UNREACHABLE() assert_noinline_call([] { LOG_CRITICAL(Debug, "Unreachable code!"); })
|
2019-10-05 07:54:07 -07:00
|
|
|
#define UNREACHABLE_MSG(...) \
|
|
|
|
assert_noinline_call([&] { LOG_CRITICAL(Debug, "Unreachable code!\n" __VA_ARGS__); })
|
2015-01-20 17:16:47 -08:00
|
|
|
|
|
|
|
#ifdef _DEBUG
|
|
|
|
#define DEBUG_ASSERT(_a_) ASSERT(_a_)
|
|
|
|
#define DEBUG_ASSERT_MSG(_a_, ...) ASSERT_MSG(_a_, __VA_ARGS__)
|
|
|
|
#else // not debug
|
2021-08-05 10:46:22 -07:00
|
|
|
#define DEBUG_ASSERT(_a_) \
|
|
|
|
do { \
|
|
|
|
} while (0)
|
|
|
|
#define DEBUG_ASSERT_MSG(_a_, _desc_, ...) \
|
|
|
|
do { \
|
|
|
|
} while (0)
|
2015-01-20 17:16:47 -08:00
|
|
|
#endif
|
|
|
|
|
2018-11-20 14:58:57 -08:00
|
|
|
#define UNIMPLEMENTED() ASSERT_MSG(false, "Unimplemented code!")
|
2018-01-07 14:43:41 -08:00
|
|
|
#define UNIMPLEMENTED_MSG(...) ASSERT_MSG(false, __VA_ARGS__)
|
common/assert: Add UNIMPLEMENTED_IF and UNIMPLEMENTED_IF_MSG for conditional assertions
Currently, there's no way to specify if an assertion should
conditionally occur due to unimplemented behavior. This is useful when
something is only partially implemented (e.g. due to ongoing RE work).
In particular, this would be useful within the graphics code.
The rationale behind this is it allows a dev to disable unimplemented
feature assertions (which can occur in an unrelated work area), while
still enabling regular assertions, which act as behavior guards for
conditions or states which must not occur. Previously, the only way a
dev could temporarily disable asserts, was to disable the regular
assertion macros, which has the downside of also disabling, well, the
regular assertions which hold more sanitizing value, as opposed to
unimplemented feature assertions.
2018-11-20 15:03:00 -08:00
|
|
|
|
|
|
|
#define UNIMPLEMENTED_IF(cond) ASSERT_MSG(!(cond), "Unimplemented code!")
|
|
|
|
#define UNIMPLEMENTED_IF_MSG(cond, ...) ASSERT_MSG(!(cond), __VA_ARGS__)
|
2019-03-27 11:59:00 -07:00
|
|
|
|
|
|
|
// If the assert is ignored, execute _b_
|
|
|
|
#define ASSERT_OR_EXECUTE(_a_, _b_) \
|
|
|
|
do { \
|
|
|
|
ASSERT(_a_); \
|
|
|
|
if (!(_a_)) { \
|
|
|
|
_b_ \
|
|
|
|
} \
|
|
|
|
} while (0)
|
|
|
|
|
|
|
|
// If the assert is ignored, execute _b_
|
|
|
|
#define ASSERT_OR_EXECUTE_MSG(_a_, _b_, ...) \
|
|
|
|
do { \
|
|
|
|
ASSERT_MSG(_a_, __VA_ARGS__); \
|
|
|
|
if (!(_a_)) { \
|
|
|
|
_b_ \
|
|
|
|
} \
|
|
|
|
} while (0)
|