llvm-project.git/lldb/test/Shell/SymbolFile/DWARF/x86/find-basic-function.cpp, branch main

[NFCI][lldb][test] Fix mismatched C/C++ substitutions (#165773)

2025-10-30T21:18:32+00:00

Most of the cases were where a C++ file was being compiled with the C substitution.
There were a few cases of the opposite though.

LLDB seems to be the only real culprit in the LLVM codebase for these mismatches.
Rest of the LLVM presumably sticks at least language-specific options in the common substitutions
making the mistakes immediately apparent.

I found these by using Clang frontend configuration files containing language-specific options for
both C and C++ (e.g. `-std=c2y` and `-std=c++26`).

[lldb] Merge CompilerContextKind::{Class,Struct} (#96145)

2024-06-24T06:56:21+00:00

Our dwarf parsing code treats structures and classes as interchangable.
CompilerContextKind is used when looking DIEs for types. This makes sure
we always they're treated the same way.

See also
[#95905#discussion_r1645686628](https://github.com/llvm/llvm-project/pull/95905#discussion_r1645686628).

[lldb/test] Add basic ld.lld --debug-names tests (#88335)

2024-04-23T18:18:05+00:00

Test that ld.lld --debug-names (#86508) built per-module index can be
consumed by lldb. This has uncovered a bug during the development of the
lld feature.

[lldb] DWARFDIE: Follow DW_AT_specification when computing CompilerCo… (#77157)

2024-01-09T18:45:30+00:00

…ntext

Following the specification chain seems to be clearly the expected
behavior of GetDeclContext(). Otherwise C++ methods have an empty
CompilerContext instead of being nested in their struct/class.

Theprimary motivation for this functionality is the Swift plugin. In
order to test the change I added a proof-of-concept implementation of a
Module::FindFunction() variant that takes a CompilerContext, expesed via
lldb-test.

rdar://120553412

Expose DWARFDIE::GetDeclContext() in lldb_private::Function. (#69981)

2023-10-24T17:55:23+00:00

I need this API in the Swift plugin, but it seems generally useful
enough to expose it in the main branch.

Reland "[lldb/DWARF] Only match mangled name in full-name function lookup (with accelerators)"

2021-08-04T10:50:13+00:00

Summary:

In the spirit of https://reviews.llvm.org/D70846, we only return functions with
matching mangled name from Apple/DebugNamesDWARFIndex::GetFunction if
eFunctionNameTypeFull is requested.

This speeds up lookup in the presence of large amount of class methods of the
same name (a typical examples would be constructors of templates with many
instantiations or overloaded operators).

Reviewers: labath, teemperor

Reviewed By: labath, teemperor

Subscribers: aprantl, arphaman, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D73191

[lldb] Require x86 backend for a bunch of DWARF tests

2021-04-13T08:47:41+00:00

By moving them into a folder with a local lit config
requiring x86. All these tests use x86 target triples.

There are two tests that require target-x86_64 because
they run program files (instead of just needing the backend).
Those are moved to the x86 folder also but their REQUIRES are
unchanged.

Reviewed By: JDevlieghere

Differential Revision: https://reviews.llvm.org/D100193