You always can just make a similar statement for the new attribute: It inherits attributes from the referenced DIE unless overridden in this DIE. Or somesuch.
On 10/12/24 17:10, Adrian Prantl wrote: > CAUTION! External Email. Do not click links or open attachments unless you > recognize the sender and are sure the content is safe. > If you think this is a phishing email, please report it by using the "Phish > Alert Report" button in Outlook. > >> On Oct 10, 2024, at 9:31 AM, Todd Allen via Dwarf-discuss >> <dwarf-discuss@lists.dwarfstd.org> wrote: >> >> Adrian, >> >> This usage of DW_AT_specification seems very different from other uses >> of DW_AT_specification, where it's indicating that the current DIE is a >> completion of a forward declaration at the referenced DIE. This usage >> is a bit closer to a "renames", but it isn't even quite that. I suggest >> not attempting to use DW_AT_specification for this case, and just >> inventing a new attribute. >> >> Todd > From the spec: > >> A debugging information entry that represents a declaration that completes >> another (earlier) non-defining declaration may have a DW_AT_specification >> attribute whose value is a reference to the debugging information entry >> representing the non-defining declaration. > You are right that this doesn't fit because in the property use-case we don't > complete a forward declaration, we just refer to it. > >> A debugging information entry with a >> DW_AT_specification attribute does not need to duplicate information provided >> by the debugging information entry referenced by that specification >> attribute. > This behavior is something I want though. > > I'll replace it with a new attribute for now. > > thanks, > Adrian -- Dwarf-discuss mailing list Dwarf-discuss@lists.dwarfstd.org https://lists.dwarfstd.org/mailman/listinfo/dwarf-discuss
