LadybirdBrowser/ladybird
1
1
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2024-12-28 13:43:45 +03:00
Code Issues Packages Projects Releases Wiki Activity
177b04dcfc
ladybird/AK/Assertions.h

29 lines
1.3 KiB
C
Raw Normal View History

Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 11:38:21 +03:00
/*
* Copyright (c) 2018-2020, Andreas Kling <kling@serenityos.org>
*
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt *
2021-04-22 11:24:48 +03:00
* SPDX-License-Identifier: BSD-2-Clause
Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 11:38:21 +03:00
*/
Import all this stuff into a single repo called Serenity.
2018-10-10 12:53:07 +03:00
#pragma once
AK: Untangle TestSuite assertions a bit
2021-02-23 10:33:03 +03:00
#if defined(KERNEL)
Everywhere: Move global Kernel pattern code to Kernel/Library directory This has KString, KBuffer, DoubleBuffer, KBufferBuilder, IOWindow, UserOrKernelBuffer and ScopedCritical classes being moved to the Kernel/Library subdirectory. Also, move the panic and assertions handling code to that directory.
2023-02-24 21:10:59 +03:00
# include <Kernel/Library/Assertions.h>
AK: Untangle TestSuite assertions a bit
2021-02-23 10:33:03 +03:00
#else
# include <assert.h>
AK: Always define ak_assertion_failed, even when NDEBUG is false Just because we may compile serenity with or without NDEBUG doesn't mean that consuming projects or Ports will share the setting. Always define the custom assertion function so that we don't have to keep the same debug settings between all projects.
2023-02-05 18:15:55 +03:00
extern "C" __attribute__((noreturn)) void ak_verification_failed(char const*);
AK: Never use assert() when targeting Windows platforms The Windows CRT definition of assert() is not noreturn, and causes compile errors when using it as the backing for VERIFY() in debug configurations of applications like the Jakt compiler.
2023-06-25 23:12:52 +03:00
# if !defined(NDEBUG) && !defined(WIN32)
AK: Make VERIFY() work in MinSizeRel builds
2022-07-08 15:16:53 +03:00
# define VERIFY assert
# else
Everywhere: Run clang-format
2022-10-17 01:06:11 +03:00
# define __stringify_helper(x) #x
AK: Print VERIFY() error messages in release builds Until now, VERIFY() failures would just cause a __builtin_trap() in release builds, which made them a bit too harsh. This commit adds an out-of-line helper function that prints the error before trapping.
2022-10-06 14:35:46 +03:00
# define __stringify(x) __stringify_helper(x)
# define VERIFY(expr) \
(__builtin_expect(!(expr), 0) \
? ak_verification_failed(#expr "\n" __FILE__ ":" __stringify(__LINE__)) \
AK: Make VERIFY() work in MinSizeRel builds
2022-07-08 15:16:53 +03:00
: (void)0)
# endif
# define VERIFY_NOT_REACHED() VERIFY(false) /* NOLINT(cert-dcl03-c,misc-static-assert) No, this can't be static_assert, it's a runtime check */
AK+Kernel: Print TODO when a TODO() is executed Previously we would just print "ASSERTION FAILED: false", which was kinda cryptic and also didn't make it clear whether this was a TODO or an unreachable condition. Now, we actually print "ASSERTION FAILED: TODO", making it crystal clear.
2021-08-03 23:02:19 +03:00
static constexpr bool TODO = false;
AK: Suppress clang-tidy warning on TODO() This adds a NOLINT directive to the definition of the TODO() macro. clang-tidy wants the assert replaced with a static_assert, since the macro simply resolves to assert(false). This is obviously nonsensical, since we want the code to still compile even with TODO(). The same fix has already been implemented for VERIFY_NOT_REACHED().
2022-02-21 19:34:19 +03:00
# define TODO() VERIFY(TODO) /* NOLINT(cert-dcl03-c,misc-static-assert) No, this can't be static_assert, it's a runtime check */
AK+Userland: Stub out code that isn't currently implemented on AARCH64 Even though this almost certainly wouldn't run properly even if we had a working kernel for AARCH64 this at least lets us build all the userland binaries.
2022-10-12 22:55:05 +03:00
# define TODO_AARCH64() VERIFY(TODO) /* NOLINT(cert-dcl03-c,misc-static-assert) No, this can't be static_assert, it's a runtime check */
TestSuite: Hijack the ASSERT macros during unit tests. Instead of aborting the program when we hit an assertion, just print a message and keep going. This allows us to write tests that provoke assertions on purpose.
2019-08-02 10:23:03 +03:00
#endif
Reference in New Issue Copy Permalink