[clang-tidy] Add new check bugprone-unintended-char-ostream-output #127720

HerrCai0907 · 2025-02-18T23:40:21Z

It wants to find unintended character output from uint8_t and int8_t to an ostream.
e.g.

uint8_t v = 9;
std::cout << v;

It wants to find unintended character output from and to an ostream. e.g. uint8_t v = 9; std::cout << v;

llvmbot · 2025-02-18T23:40:53Z

@llvm/pr-subscribers-clang-tools-extra

@llvm/pr-subscribers-clang-tidy

Author: Congcong Cai (HerrCai0907)

Changes

It wants to find unintended character output from uint8_t and int8_t to an ostream.
e.g.

uint8_t v = 9;
std::cout &lt;&lt; v;

Full diff: https://github.com/llvm/llvm-project/pull/127720.diff

8 Files Affected:

(modified) clang-tools-extra/clang-tidy/bugprone/BugproneTidyModule.cpp (+3)
(modified) clang-tools-extra/clang-tidy/bugprone/CMakeLists.txt (+1)
(added) clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.cpp (+70)
(added) clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.h (+34)
(modified) clang-tools-extra/docs/ReleaseNotes.rst (+6)
(added) clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst (+30)
(modified) clang-tools-extra/docs/clang-tidy/checks/list.rst (+1)
(added) clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp (+70)

diff --git a/clang-tools-extra/clang-tidy/bugprone/BugproneTidyModule.cpp b/clang-tools-extra/clang-tidy/bugprone/BugproneTidyModule.cpp
index c5f0b5b28418f..0a3376949b6e5 100644
--- a/clang-tools-extra/clang-tidy/bugprone/BugproneTidyModule.cpp
+++ b/clang-tools-extra/clang-tidy/bugprone/BugproneTidyModule.cpp
@@ -90,6 +90,7 @@
 #include "UndelegatedConstructorCheck.h"
 #include "UnhandledExceptionAtNewCheck.h"
 #include "UnhandledSelfAssignmentCheck.h"
+#include "UnintendedCharOstreamOutputCheck.h"
 #include "UniquePtrArrayMismatchCheck.h"
 #include "UnsafeFunctionsCheck.h"
 #include "UnusedLocalNonTrivialVariableCheck.h"
@@ -147,6 +148,8 @@ class BugproneModule : public ClangTidyModule {
         "bugprone-incorrect-enable-if");
     CheckFactories.registerCheck<IncorrectEnableSharedFromThisCheck>(
         "bugprone-incorrect-enable-shared-from-this");
+    CheckFactories.registerCheck<UnintendedCharOstreamOutputCheck>(
+        "bugprone-unintended-char-ostream-output");
     CheckFactories.registerCheck<ReturnConstRefFromParameterCheck>(
         "bugprone-return-const-ref-from-parameter");
     CheckFactories.registerCheck<SwitchMissingDefaultCaseCheck>(
diff --git a/clang-tools-extra/clang-tidy/bugprone/CMakeLists.txt b/clang-tools-extra/clang-tidy/bugprone/CMakeLists.txt
index e8309c68b7fca..9758d7259bf65 100644
--- a/clang-tools-extra/clang-tidy/bugprone/CMakeLists.txt
+++ b/clang-tools-extra/clang-tidy/bugprone/CMakeLists.txt
@@ -29,6 +29,7 @@ add_clang_library(clangTidyBugproneModule STATIC
   InaccurateEraseCheck.cpp
   IncorrectEnableIfCheck.cpp
   IncorrectEnableSharedFromThisCheck.cpp
+  UnintendedCharOstreamOutputCheck.cpp
   ReturnConstRefFromParameterCheck.cpp
   SuspiciousStringviewDataUsageCheck.cpp
   SwitchMissingDefaultCaseCheck.cpp
diff --git a/clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.cpp b/clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.cpp
new file mode 100644
index 0000000000000..7c54ef1486b2f
--- /dev/null
+++ b/clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.cpp
@@ -0,0 +1,70 @@
+//===--- UnintendedCharOstreamOutputCheck.cpp - clang-tidy
+//---------------------===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+//
+//===----------------------------------------------------------------------===//
+
+#include "UnintendedCharOstreamOutputCheck.h"
+#include "clang/AST/Type.h"
+#include "clang/ASTMatchers/ASTMatchFinder.h"
+#include "clang/ASTMatchers/ASTMatchers.h"
+
+using namespace clang::ast_matchers;
+
+namespace clang::tidy::bugprone {
+
+namespace {
+
+// check if the type is unsigned char or signed char
+AST_MATCHER(Type, isNumericChar) {
+  const auto *BT = dyn_cast<BuiltinType>(&Node);
+  if (BT == nullptr)
+    return false;
+  const BuiltinType::Kind K = BT->getKind();
+  return K == BuiltinType::UChar || K == BuiltinType::SChar;
+}
+
+// check if the type is char
+AST_MATCHER(Type, isChar) {
+  const auto *BT = dyn_cast<BuiltinType>(&Node);
+  if (BT == nullptr)
+    return false;
+  const BuiltinType::Kind K = BT->getKind();
+  return K == BuiltinType::Char_U || K == BuiltinType::Char_S;
+}
+
+} // namespace
+
+void UnintendedCharOstreamOutputCheck::registerMatchers(MatchFinder *Finder) {
+  auto BasicOstream =
+      cxxRecordDecl(hasName("::std::basic_ostream"),
+                    // only basic_ostream<char, Traits> has overload operator<<
+                    // with char / unsigned char / signed char
+                    classTemplateSpecializationDecl(
+                        hasTemplateArgument(0, refersToType(isChar()))));
+  Finder->addMatcher(
+      cxxOperatorCallExpr(
+          hasOverloadedOperatorName("<<"),
+          hasLHS(hasType(hasUnqualifiedDesugaredType(
+              recordType(hasDeclaration(cxxRecordDecl(
+                  anyOf(BasicOstream, isDerivedFrom(BasicOstream)))))))),
+          hasRHS(hasType(hasUnqualifiedDesugaredType(isNumericChar()))))
+          .bind("x"),
+      this);
+}
+
+void UnintendedCharOstreamOutputCheck::check(
+    const MatchFinder::MatchResult &Result) {
+  const auto *Call = Result.Nodes.getNodeAs<CXXOperatorCallExpr>("x");
+  const Expr *Value = Call->getArg(1);
+  diag(Call->getOperatorLoc(),
+       "(%0 passed to 'operator<<' outputs as character instead of integer. "
+       "cast to 'unsigned' to print numeric value or cast to 'char' to print "
+       "as character)")
+      << Value->getType() << Value->getSourceRange();
+}
+
+} // namespace clang::tidy::bugprone
diff --git a/clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.h b/clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.h
new file mode 100644
index 0000000000000..071baac3216c0
--- /dev/null
+++ b/clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.h
@@ -0,0 +1,34 @@
+//===--- UnintendedCharOstreamOutputCheck.h - clang-tidy --------*- C++ -*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+//
+//===----------------------------------------------------------------------===//
+
+#ifndef LLVM_CLANG_TOOLS_EXTRA_CLANG_TIDY_BUGPRONE_UNINTENDEDCHAROSTREAMOUTPUTCHECK_H
+#define LLVM_CLANG_TOOLS_EXTRA_CLANG_TIDY_BUGPRONE_UNINTENDEDCHAROSTREAMOUTPUTCHECK_H
+
+#include "../ClangTidyCheck.h"
+
+namespace clang::tidy::bugprone {
+
+/// Finds unintended character output from `unsigned char` and `signed char` to
+/// an ostream.
+///
+/// For the user-facing documentation see:
+/// http://clang.llvm.org/extra/clang-tidy/checks/bugprone/unintended-char-ostream-output.html
+class UnintendedCharOstreamOutputCheck : public ClangTidyCheck {
+public:
+  UnintendedCharOstreamOutputCheck(StringRef Name, ClangTidyContext *Context)
+      : ClangTidyCheck(Name, Context) {}
+  void registerMatchers(ast_matchers::MatchFinder *Finder) override;
+  void check(const ast_matchers::MatchFinder::MatchResult &Result) override;
+  bool isLanguageVersionSupported(const LangOptions &LangOpts) const override {
+    return LangOpts.CPlusPlus;
+  }
+};
+
+} // namespace clang::tidy::bugprone
+
+#endif // LLVM_CLANG_TOOLS_EXTRA_CLANG_TIDY_BUGPRONE_UNINTENDEDCHAROSTREAMOUTPUTCHECK_H
diff --git a/clang-tools-extra/docs/ReleaseNotes.rst b/clang-tools-extra/docs/ReleaseNotes.rst
index 6b8fe22242417..57f37c8e02e2e 100644
--- a/clang-tools-extra/docs/ReleaseNotes.rst
+++ b/clang-tools-extra/docs/ReleaseNotes.rst
@@ -91,6 +91,12 @@ Improvements to clang-tidy
 New checks
 ^^^^^^^^^^
 
+- New :doc:`bugprone-unintended-char-ostream-output
+  <clang-tidy/checks/bugprone/unintended-char-ostream-output>` check.
+
+  Finds unintended character output from `unsigned char` and `signed char` to an
+  ostream.
+
 New check aliases
 ^^^^^^^^^^^^^^^^^
 
diff --git a/clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst b/clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst
new file mode 100644
index 0000000000000..1e60698a5d445
--- /dev/null
+++ b/clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst
@@ -0,0 +1,30 @@
+.. title:: clang-tidy - bugprone-unintended-char-ostream-output
+
+bugprone-unintended-char-ostream-output
+=======================================
+
+Finds unintended character output from `unsigned char` and `signed char` to an
+``ostream``.
+
+Normally, when ``unsigned char (uint8_t)`` or ``signed char (int8_t)`` is used, it
+is more likely a number than a character. However, when it is passed directly to
+``std::ostream``'s ``operator<<``, resulting in character-based output instead
+of numeric value. This often contradicts the developer's intent to print
+integer values.
+
+.. code-block:: c++
+
+    uint8_t v = 9;
+    std::cout << v; // output '\t' instead of '9'
+
+It could be fixed as
+
+.. code-block:: c++
+
+    std::cout << (uint32_t)v;
+
+Or cast to char to explicitly indicate the intent
+
+.. code-block:: c++
+
+    std::cout << (char)v;
diff --git a/clang-tools-extra/docs/clang-tidy/checks/list.rst b/clang-tools-extra/docs/clang-tidy/checks/list.rst
index 7b9b905ef7671..9306dfe95fa45 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/list.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/list.rst
@@ -158,6 +158,7 @@ Clang-Tidy Checks
    :doc:`bugprone-undelegated-constructor <bugprone/undelegated-constructor>`,
    :doc:`bugprone-unhandled-exception-at-new <bugprone/unhandled-exception-at-new>`,
    :doc:`bugprone-unhandled-self-assignment <bugprone/unhandled-self-assignment>`,
+   :doc:`bugprone-unintended-char-ostream-output <bugprone/unintended-char-ostream-output>`,
    :doc:`bugprone-unique-ptr-array-mismatch <bugprone/unique-ptr-array-mismatch>`, "Yes"
    :doc:`bugprone-unsafe-functions <bugprone/unsafe-functions>`,
    :doc:`bugprone-unused-local-non-trivial-variable <bugprone/unused-local-non-trivial-variable>`,
diff --git a/clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp b/clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp
new file mode 100644
index 0000000000000..fd2382dcd730c
--- /dev/null
+++ b/clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp
@@ -0,0 +1,70 @@
+// RUN: %check_clang_tidy %s bugprone-unintended-char-ostream-output %t
+
+namespace std {
+
+template <class _CharT, class _Traits = void> class basic_ostream {
+public:
+  basic_ostream &operator<<(int);
+  basic_ostream &operator<<(unsigned int);
+};
+
+template <class CharT, class Traits>
+basic_ostream<CharT, Traits> &operator<<(basic_ostream<CharT, Traits> &, CharT);
+template <class CharT, class Traits>
+basic_ostream<CharT, Traits> &operator<<(basic_ostream<CharT, Traits> &, char);
+template <class _Traits>
+basic_ostream<char, _Traits> &operator<<(basic_ostream<char, _Traits> &, char);
+template <class _Traits>
+basic_ostream<char, _Traits> &operator<<(basic_ostream<char, _Traits> &,
+                                          signed char);
+template <class _Traits>
+basic_ostream<char, _Traits> &operator<<(basic_ostream<char, _Traits> &,
+                                          unsigned char);
+
+using ostream = basic_ostream<char>;
+
+
+} // namespace std
+
+class A : public std::ostream {};
+
+void origin_ostream(std::ostream &os) {
+  unsigned char unsigned_value = 9;
+  os << unsigned_value;
+  // CHECK-MESSAGES: [[@LINE-1]]:6: warning: ('unsigned char' passed to
+  // 'operator<<' outputs as character instead of integer
+
+  signed char signed_value = 9;
+  os << signed_value;
+  // CHECK-MESSAGES: [[@LINE-1]]:6: warning: ('signed char' passed to
+  // 'operator<<' outputs as character instead of integer
+
+  char char_value = 9;
+  os << char_value;
+}
+
+void based_on_ostream(A &os) {
+  unsigned char unsigned_value = 9;
+  os << unsigned_value;
+  // CHECK-MESSAGES: [[@LINE-1]]:6: warning: ('unsigned char' passed to
+  // 'operator<<' outputs as character instead of integer
+
+  signed char signed_value = 9;
+  os << signed_value;
+  // CHECK-MESSAGES: [[@LINE-1]]:6: warning: ('signed char' passed to
+  // 'operator<<' outputs as character instead of integer
+
+  char char_value = 9;
+  os << char_value;
+}
+
+void based_on_ostream(std::basic_ostream<unsigned char> &os) {
+  unsigned char unsigned_value = 9;
+  os << unsigned_value;
+
+  signed char signed_value = 9;
+  os << signed_value;
+
+  char char_value = 9;
+  os << char_value;
+}

clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.cpp

clang-tools-extra/docs/ReleaseNotes.rst

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst

clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst

clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst

PiotrZSL

Overall looks fine for me, just few things to point out.

PiotrZSL · 2025-02-19T13:18:16Z

clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.cpp

+       "%0 passed to 'operator<<' outputs as character instead of integer. "
+       "cast to 'unsigned' to print numeric value or cast to 'char' to print "
+       "as character")
+      << Value->getType() << Value->getSourceRange();


You could generate auto-fixes, easiest way is to insert "+" character before such, in that case it will be cast to int

That's a fairly obscure solution, relying on implicit arithmetic promotions. It's banned in some coding guidelines (e.g. MISRA). Maybe just add an explicit static_cast<int>? Otherwise give the option to the user to choose what datatype to cast to, defaulting to int.

The problem with int versus unsigned int is that in case you're on a platform where sizeof(char) == sizeof(int) then casting a value that happens to encode to a negative integer will result in the printing of a negative number. Not sure if this is something intentional.

(Nevertheless, I would prefer if the warning said unsigned int instead of just unsigned. It's non-trivial to know that unsigned alone is perfectly fine and actually means the same thing as unsinged int.)

I think easiest is to just let the user decide what type they want to use, keeping some sane default (unsigned int is fine IMO).

Some guidelines also ban the usage of built-in types like int and require you to use std::int32_t instead to be explicit. Having an option would allow the user to specify that.

For me, it is more clearer to cast unsigned char to unsigned int and signed char to int. This can avoid that when converting unsigned char to int, people are not sure whether the result of 255 is -1 or 255.

Given the range only suggesting int should be safe. Adding unsigned in case the underlying type would make it more clearer though.

As in other cases I think it should be coding guideline agnostic and suggest the least intrusive (e.g. std::int32_t requires the <cstdint> include). But let's not start that discussion again...

requires the include

Fair point. Perhaps just cast to int is the best compromise. It is also what unary plus does. If users need more flexibility we can add an option later.

option is already added.

clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp

clang-tools-extra/clang-tidy/bugprone/UnintendedCharOstreamOutputCheck.cpp

PiotrZSL · 2025-02-19T13:29:43Z

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst

+
+.. code-block:: c++
+
+    std::cout << static_cast<uint32_t>(v);


or

std::cout << +v;

I think it is quiet magic and relies on the developer's familiarity with the C++ specification

It is "magic" but I think it might make sense to make sure that the warning is not triggered by it.

Absolutely, this is a valid code pattern (magic or not) that the tool should not warn about.

In the docs, if wanted, we could mention both cases as examples, and also explain that unary plus leads to the same result as static_cast<int>.

clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp

clang-tools-extra/docs/ReleaseNotes.rst

…har-ostream-output.rst Co-authored-by: whisperity <[email protected]>

clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp

…har-ostream-output

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst

…lvm#127720) It wants to find unintended character output from `uint8_t` and `int8_t` to an ostream. e.g. ```c++ uint8_t v = 9; std::cout << v; ``` --------- Co-authored-by: whisperity <[email protected]>

firewave · 2025-03-17T14:30:29Z

Some thoughts based on the warnings I am seeing in actual code.

Another way to fix this could be using std::to_string().

I am seeing this with an enum type which might be valid, working code but have not looked into it yet.

The fix-it is problematic if it is a templated type and should probably be omitted in that case:

#include <cstdint>
#include <sstream>

template<typename T>
void func(const T& data)
{
    std::ostringstream ostr;
    ostr << data;
}

void f()
{
    func((char)0);
    func((int8_t)0);
    func("");
}

<source>:8:10: warning: 'signed char' passed to 'operator<<' outputs as character instead of integer. cast to 'unsigned int' to print numeric value or cast to 'char' to print as character [bugprone-unintended-char-ostream-output]
    8 |     ostr << data;
      |          ^  ~~~~
      |             static_cast<int>(data)

https://godbolt.org/z/93axK1E4M

firewave · 2025-03-27T10:44:25Z

I am seeing this with an enum type which might be valid, working code but have not looked into it yet.

The warnings in question were correct. It exposed a behavior change introduced by fixing performance-enum-size.

[clang-tidy]add new check bugprone-unintended-char-ostream-output

b69bb46

It wants to find unintended character output from and to an ostream. e.g. uint8_t v = 9; std::cout << v;

HerrCai0907 requested review from PiotrZSL and 5chmidti February 18, 2025 23:40

llvmbot added clang-tools-extra clang-tidy labels Feb 18, 2025

HerrCai0907 requested a review from EugeneZelenko February 18, 2025 23:40

EugeneZelenko reviewed Feb 18, 2025

View reviewed changes

fix review

22b8bd8

carlosgalvezp reviewed Feb 19, 2025

View reviewed changes

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst Outdated Show resolved Hide resolved

carlosgalvezp reviewed Feb 19, 2025

View reviewed changes

clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp Outdated Show resolved Hide resolved

fix review

9033197

HerrCai0907 force-pushed the bugprone/unintended-char-ostream-output branch from 03eacf4 to 9033197 Compare February 19, 2025 09:54

whisperity reviewed Feb 19, 2025

View reviewed changes

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst Outdated Show resolved Hide resolved

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst Outdated Show resolved Hide resolved

PiotrZSL reviewed Feb 19, 2025

View reviewed changes

whisperity changed the title ~~[clang-tidy]add new check bugprone-unintended-char-ostream-output~~ [clang-tidy] Add new check bugprone-unintended-char-ostream-output Feb 19, 2025

EugeneZelenko reviewed Feb 19, 2025

View reviewed changes

clang-tools-extra/docs/ReleaseNotes.rst Outdated Show resolved Hide resolved

HerrCai0907 and others added 2 commits February 20, 2025 08:01

Update clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-c…

824f287

…har-ostream-output.rst Co-authored-by: whisperity <[email protected]>

fix review

7f6405e

EugeneZelenko reviewed Feb 20, 2025

View reviewed changes

clang-tools-extra/test/clang-tidy/checkers/bugprone/unintended-char-ostream-output.cpp Show resolved Hide resolved

HerrCai0907 added 3 commits February 20, 2025 08:35

template test

00df49d

add more test case

bc43f1f

add option

82cb4d0

HerrCai0907 requested review from PiotrZSL, EugeneZelenko, carlosgalvezp and whisperity February 20, 2025 22:26

HerrCai0907 added 2 commits February 24, 2025 13:16

rework doc

553d6cd

Merge remote-tracking branch 'origin/main' into bugprone/unintended-c…

2ec0afd

…har-ostream-output

HerrCai0907 requested a review from firewave February 24, 2025 05:17

carlosgalvezp reviewed Feb 24, 2025

View reviewed changes

clang-tools-extra/docs/clang-tidy/checks/bugprone/unintended-char-ostream-output.rst Outdated Show resolved Hide resolved

add doc

4d3916e

HerrCai0907 merged commit 56762b7 into llvm:main Feb 27, 2025
12 checks passed

HerrCai0907 deleted the bugprone/unintended-char-ostream-output branch February 27, 2025 11:36

huaatian mentioned this pull request Feb 28, 2025

fix live interval empty issue huaatian/llvm-project#1

Open

firewave mentioned this pull request Apr 13, 2025

misleading fix-it with bugprone-unintended-char-ostream-output in templated code #135558

Open

[clang-tidy] Add new check bugprone-unintended-char-ostream-output #127720

[clang-tidy] Add new check bugprone-unintended-char-ostream-output #127720

Uh oh!

Conversation

HerrCai0907 commented Feb 18, 2025

Uh oh!

llvmbot commented Feb 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

PiotrZSL left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

firewave commented Mar 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

firewave commented Mar 27, 2025

Uh oh!

Uh oh!

llvmbot commented Feb 18, 2025 •

edited

Loading

firewave commented Mar 17, 2025 •

edited

Loading