Thanks so much for the quick response David.
I have reported this as a bug on GCC's bug tracker:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118117
I tried it on clang and I don't see the same behavior. So it does seem to
be pointing to an issue in GCC...
Thanks
Lorenzo
On Wed, Dec 18, 2024 at
David Blaikie wrote:
>
> What sort of string-like behavior would one want on a bit-string? Seems
> like array would be the better fit to me...
>
It's a language that originates in the late 60s - so there are some,
"different" ideas than more contemporary languages.
You can ask for sub-string
This is probably more of a question for the DWARF producer, like GCC, than
the DWARF workgroup, but let's take a look anyway...
Ah, OK, simplifying things down a bit. You've got this case:
```
struct t1
{
typedef struct
{
} t2;
#ifdef USE_VIRTUAL
virtual void f1();
#endif
};
t1::
What sort of string-like behavior would one want on a bit-string? Seems
like array would be the better fit to me...
On Wed, Dec 18, 2024 at 9:03 AM pogo 59 via Dwarf-discuss <
dwarf-discuss@lists.dwarfstd.org> wrote:
> My first thought would be that DW_TAG_string_type with a one-bit base
> type,
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
PL/I has the concept of a "string", which can be a fixed-length
(possibly not known at compile time), or a fixed size with a 4-byte or 2-byte
runtime length prefix, or, depending on the consituents, a NULL (zero-byte)
terminated string.
For "character-like" strings, the constituents can be 1-byt
