main

GGitHub[lldb][TypeSystem] Remove count parameter from TypeSystem::IsFloatingPointType (#165707)

b81a9927创建于 2025年10月31日历史提交

文件	最后提交记录	最后更新时间
ABIARM.cpp	[lldb/Plugin] s/LLDB_PLUGIN/LLDB_PLUGIN_DEFINE/ (NFC) Rename LLDB_PLUGIN to LLDB_PLUGIN_DEFINE as Pavel suggested in D73067 to avoid name conflict.	6 年前
ABIARM.h	[lldb] Update header guards to be consistent and compliant with LLVM (NFC) LLDB has a few different styles of header guards and they're not very consistent because things get moved around or copy/pasted. This patch unifies the header guards across LLDB and converts everything to match LLVM's style. Differential revision: https://reviews.llvm.org/D74743	6 年前
ABIMacOSX_arm.cpp	[lldb][TypeSystem] Remove count parameter from TypeSystem::IsFloatingPointType (#165707) Similar motivation to https://github.com/llvm/llvm-project/pull/165702. It was unused in all callsites and inconsistent with other APIs like IsIntegerType (which doesn't take a count parameter). If we ever need a "how many elements does this type represent", we can implement one with a new TypeSystem API that does exactly that. Some callsites checked for count == 1 previously, but I suspect what they intended to do is check for whether it's a vector type or complex type, before reading the FP register. I'm somewhat confident that's the case because the TypeSystemClang::GetTypeInfo currently incorrectly sets the integer and floating point bits for complex and vector types (will fix separately). But some architectures might choose to pass single-element vectors in scalar registers. I should probably changes these to check the vector element size. All the count == 2 && is_complex were redundant because count == 2 iff is_complex == true. So I just removed the count check there.	9 个月前
ABIMacOSX_arm.h	[lldb] Modernize ABI-based unwind plan creation (#128505) Replace the by-ref return value with an actual result.	1 年前
ABISysV_arm.cpp	[lldb][TypeSystem] Remove count parameter from TypeSystem::IsFloatingPointType (#165707) Similar motivation to https://github.com/llvm/llvm-project/pull/165702. It was unused in all callsites and inconsistent with other APIs like IsIntegerType (which doesn't take a count parameter). If we ever need a "how many elements does this type represent", we can implement one with a new TypeSystem API that does exactly that. Some callsites checked for count == 1 previously, but I suspect what they intended to do is check for whether it's a vector type or complex type, before reading the FP register. I'm somewhat confident that's the case because the TypeSystemClang::GetTypeInfo currently incorrectly sets the integer and floating point bits for complex and vector types (will fix separately). But some architectures might choose to pass single-element vectors in scalar registers. I should probably changes these to check the vector element size. All the count == 2 && is_complex were redundant because count == 2 iff is_complex == true. So I just removed the count check there.	9 个月前
ABISysV_arm.h	[lldb] Modernize ABI-based unwind plan creation (#128505) Replace the by-ref return value with an actual result.	1 年前
CMakeLists.txt	[lldb/cmake] Implicitly pass arguments to llvm_add_library (#142583) If we're not touching them, we don't need to do anything special to pass them along -- with one important caveat: due to how cmake arguments work, the implicitly passed arguments need to be specified before arguments that we handle. This isn't particularly nice, but the alternative is enumerating all arguments that can be used by llvm_add_library and the macros it calls (it also relies on implicit passing of some arguments to llvm_process_sources).	1 年前