My first thought would be that DW_TAG_string_type with a one-bit base type,
but it's not clear that the other attributes would be interpreted in a way
that correctly navigated the bit string. You could try using
DW_TAG_packed_type pointing to a DW_TAG_string_type, in the hopes that
consumers would
Sorry, meant to reply-all.
-- Forwarded message -
From: pogo 59
Date: Wed, Nov 20, 2024 at 12:47 PM
Subject: Re: [Dwarf-discuss] defaulting to C23 in GCC
To: Mark Wielaard
I think it's reasonable to add codes such as this at least until DWARF v6
is published. It's just a list o
Hi Andrew,
I agree that the language could be tidied up here, but I'm confident that a
lookup of the "containing scope" ought to start with the DIE itself.
Normally any DIE describing a code entity (function, lexical block, unit)
would itself have a low_pc/high_pc pair or DW_AT_ranges; if it doesn
> Maybe this is something we could submit for standardization?
Definitely.
--paulr
On Wed, Sep 4, 2024 at 8:49 AM Felipe de Azevedo Piovezan via Dwarf-discuss
wrote:
> David has pretty much summed it up, but to restate:
>
> When we implemented this, we had to be able to distinguish the two cas
