Sounds like this is what
https://github.com/llvm/llvm-project/pull/130255 is trying to achieve?
If we could simplify that part of LLDB that'd be great!
On Wed, 23 Apr 2025 at 16:32, Kyle Huey via Dwarf-discuss
wrote:
>
> Consider the following C++ program
>
> #include
>
> class Base {
> public:
# Allow alternate encoding of DW_AT_object_pointer as a variable index
instead of DIE reference
## Background
`DW_AT_object_pointer` is used by LLDB to conveniently determine the
CV-qualifiers
and storage class of C++ member functions when reconstructing types from DWARF.
GCC currently emits `DW_
Thanks for filing
Mind updating the issue with the latest proposal I attached earlier? I.e.,
we’ll just remove the wording in the current spec
Many thanks,
Michael
On Thu, Jan 23, 2025 at 20:35 Cary Coutant wrote:
> On Wed, Jan 22, 2025 at 2:54 AM Michael Buch via Dwarf-discuss <
&
# DW_AT_object_pointer: clarify wording around implicit versus
explicit object parameters
## Background
With C++23 we got the ability to explicitly spell out in source the
object parameter of a class method [1]. The object parameter for such
methods is not compiler-generated and is explicitly nam