github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {clang-format}-->


:warning: C/C++ code formatter, clang-format found issues in your code. 
:warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
git-clang-format --diff 9cf9cb271bf86bda4996be9a31fa413381f2f5e3 
8d05d535a1c9f091e5c90af0a2e6969c57e26405 -- 
lldb/include/lldb/Symbol/CompilerType.h lldb/include/lldb/Symbol/Type.h 
lldb/include/lldb/Symbol/TypeSystem.h 
lldb/source/Plugins/SymbolFile/DWARF/DWARFASTParserClang.cpp 
lldb/source/Plugins/TypeSystem/Clang/TypeSystemClang.cpp 
lldb/source/Plugins/TypeSystem/Clang/TypeSystemClang.h 
lldb/source/Symbol/CompilerType.cpp lldb/source/Symbol/Type.cpp 
lldb/source/Symbol/TypeSystem.cpp 
lldb/unittests/SymbolFile/DWARF/DWARFASTParserClangTests.cpp
``````````

</details>

<details>
<summary>
View the diff from clang-format here.
</summary>

``````````diff
diff --git a/lldb/source/Symbol/Type.cpp b/lldb/source/Symbol/Type.cpp
index 6fa08236c1..60ad7bc029 100644
--- a/lldb/source/Symbol/Type.cpp
+++ b/lldb/source/Symbol/Type.cpp
@@ -484,11 +484,11 @@ std::optional<uint64_t> 
Type::GetByteSize(ExecutionContextScope *exe_scope) {
     case eEncodingIsLValueReferenceUID:
     case eEncodingIsRValueReferenceUID:
     case eEncodingIsLLVMPtrAuthUID: {
-    if (ArchSpec arch = m_symbol_file->GetObjectFile()->GetArchitecture()) {
-      m_byte_size = arch.GetAddressByteSize();
-      m_byte_size_has_value = true;
-      return static_cast<uint64_t>(m_byte_size);
-    }
+      if (ArchSpec arch = m_symbol_file->GetObjectFile()->GetArchitecture()) {
+        m_byte_size = arch.GetAddressByteSize();
+        m_byte_size_has_value = true;
+        return static_cast<uint64_t>(m_byte_size);
+      }
     } break;
   }
   return {};

``````````

</details>


https://github.com/llvm/llvm-project/pull/84387
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to