On Mon, 07 Jun 2021 20:27:39 +0200, David Blaikie via Dwarf-Discuss wrote:
> Ah, in the sense that you want to be able to derive new types based on
> the DWARF?
> Fair enough.
The real reason is that when using the derived class C LLDB+LLVM layout engine
will assert because FieldOffsets from DWARF
Ah, in the sense that you want to be able to derive new types based on
the DWARF?
Fair enough.
Raphael's suggestion seems reasonable to me.
On Mon, Jun 7, 2021 at 11:20 AM Jan Kratochvil
wrote:
>
> On Mon, 07 Jun 2021 20:11:16 +0200, David Blaikie via Dwarf-Discuss wrote:
> > On Mon, Jun 7, 2021
On Mon, 07 Jun 2021 20:11:16 +0200, David Blaikie via Dwarf-Discuss wrote:
> On Mon, Jun 7, 2021 at 10:58 AM Jan Kratochvil via Dwarf-Discuss
> wrote:
> >
> > clang-12 will create the same DWARF for class B with [[no_unique_address]]
> > either present or not. Despite that class C derived from B
On Mon, Jun 7, 2021 at 10:58 AM Jan Kratochvil via Dwarf-Discuss
wrote:
>
> Hi,
>
> clang-12 will create the same DWARF for class B with [[no_unique_address]]
> either present or not. Despite that class C derived from B has different
> layout depending on from which class B it gets derived
Why is
Hi,
clang-12 will create the same DWARF for class B with [[no_unique_address]]
either present or not. Despite that class C derived from B has different
layout depending on from which class B it gets derived:
--
struct A {
