[AMD Official Use Only - General]
Background
==
The vendor extension encoding space for DWARF expression operations
accommodates only 32 unique operations. In practice, the lack of a central
registry and a desire for backwards compatibility means vendor extensions are
never retired, even
attribute,
that can be done in a different proposal.
Scott
On 2018-02-01 17:32, Michael Eager wrote:
On 02/01/2018 08:07 AM, sc...@scottlinder.com wrote:
Hi John,
In the case where the files are actually available on disk, and the
source is simply being "cached", the attributes are e
approach?
Scott
On 2018-02-01 17:20, Michael Eager wrote:
On 02/01/2018 12:01 PM, sc...@scottlinder.com wrote:
Hi Paul,
My intention was to support an empty source string; I want to be
explicit about the presence of embedded source for each file.
I'm not fond of the belt and suspe
explicit here.
Scott
On 2018-02-01 11:19, paul.robin...@sony.com wrote:
-Original Message-
From: Dwarf-Discuss [mailto:dwarf-discuss-boun...@lists.dwarfstd.org]
On
Behalf Of sc...@scottlinder.com
Sent: Wednesday, January 31, 2018 2:05 PM
To: dwarf-discuss@lists.dwarfstd.org
Subject: [Dwarf
st provide an identifier to distinguish sources.
The remaining attributes (DW_AT_language, DW_AT_producer, etc.) seem
pretty naturally orthogonal.
Regards,
Scott
On 2018-01-31 14:40, John DelSignore wrote:
Hi Scott,
Question: What does the DW_TAG_compile_unit look like for an embedded
source
the next version of
the
specification.
Regards,
Scott Linder
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
