https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61595
--- Comment #6 from Sebastian Meyer ---
Ah, okay, thank you for the clarification, Jakub.
So this is indeed RESOLVED INVALID, sorry.
I am still sure I saw the example I gave, but can't seem to find it now.
Chances are good though it wasn't GCC,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61595
--- Comment #4 from Sebastian Meyer ---
Richard: The typdef gets optimized away very quickly, so I needed to trick
around a bit. But the array won't use the typedef anyway, the produced DWARF is
equal to what was produced before (DWARF3 keeps it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61595
--- Comment #1 from Sebastian Meyer ---
Created attachment 32999
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32999&action=edit
Example source, produced DWARF information and memory dump
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc-bugzilla at mailhell dot seb7.de
While writing a DWARF parser/interpreter I hit what seems to be inconsistent
DWARF information.
The original source for my example originates from
"l
