[all-commits] [llvm/llvm-project] 7b7d41: [lldb] Fix `FindDirectNestedType` not working with...
Vlad Serebrennikov via All-commits
all-commits at lists.llvm.org
Fri Feb 16 08:40:38 PST 2024
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 7b7d411de9f731d2bcf6b093f6cee2cf57a5196e
https://github.com/llvm/llvm-project/commit/7b7d411de9f731d2bcf6b093f6cee2cf57a5196e
Author: Vlad Serebrennikov <serebrennikov.vladislav at gmail.com>
Date: 2024-02-16 (Fri, 16 Feb 2024)
Changed paths:
M lldb/source/Plugins/TypeSystem/Clang/TypeSystemClang.cpp
M lldb/test/API/python_api/type/TestTypeList.py
M lldb/test/API/python_api/type/main.cpp
Log Message:
-----------
[lldb] Fix `FindDirectNestedType` not working with class templates (#81666)
This patch attempts to fix lookup in class template specialization.
The first fixed problem is that during type lookup `DeclContextGetName`
have been dropping template arguments. So when such a name was compared
against a name in `DW_AT_name`, which contains template arguments, false
mismatches have been occurring.
The second fixed problem is that LLDB's printing policy hasn't been
matching Clang's printing policy when it comes to integral non-type
template arguments. This again caused some false mismatches during type
lookup, because Clang puts e.g. `3U` in debug info for class
specializations, but LLDB has been expecting just `3`. This patch brings
printing policy in line with what Clang does.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list