0
Files
src/base/check_example.cc
Peter Kasting fa48899e70 Switch to [[(un)likely]]: base/
C++20 adds [[(un)likely]], which is being allowed. This should replace
our existing macro usage.

Bug: 40256217
Change-Id: I833f2272f01dc5e4e0f1ac5fe2937e7bf511f6b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5763878
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1337712}
2024-08-06 07:48:14 +00:00

42 lines
1.2 KiB
C++

// Copyright 2011 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
// This file is meant for analyzing the code generated by the CHECK
// macros in a small executable file that's easy to disassemble.
#include <ostream>
#include "base/check_op.h"
#include "base/compiler_specific.h"
// An official build shouldn't generate code to print out messages for
// the CHECK* macros, nor should it have the strings in the
// executable. It is also important that the CHECK() function collapse to the
// same implementation as RELEASE_ASSERT(), in particular on Windows x86.
// Historically, the stream eating caused additional unnecessary instructions.
// See https://crbug.com/672699.
#define BLINK_RELEASE_ASSERT_EQUIVALENT(assertion) \
if (!(assertion)) [[unlikely]] { \
base::ImmediateCrash(); \
}
void DoCheck(bool b) {
CHECK(b) << "DoCheck " << b;
}
void DoBlinkReleaseAssert(bool b) {
BLINK_RELEASE_ASSERT_EQUIVALENT(b);
}
void DoCheckEq(int x, int y) {
CHECK_EQ(x, y);
}
int main(int argc, const char* argv[]) {
DoCheck(argc > 1);
DoCheckEq(argc, 1);
DoBlinkReleaseAssert(argc > 1);
}