To add to what Greg described you may also want to look at section 6.4.4 of the
DWARF 5 specification that discusses these issues. In particular note the
non-normative description in the fourth paragraph.
> 6.4.4 Call Frame Calling Address
>
> *When virtually unwinding frames, consumers frequen
A compiler may promote part of a variable to a scratch pad memory address space.
Thanks,
-Tony Tye
-Original Message-
From: Michael Eager
On 7/30/20 5:17 PM, Tye, Tony via Dwarf-Discuss wrote:
> For optimized code involving multiple address spaces it is possible to
> run into
For optimized code involving multiple address spaces it is possible to run into
cases where the location of a source language variable requires multiple
address spaces. For example, a source variable may be optimized and different
pieces may be in different places including memory of multiple ad
Another question that has been raised as part of the HSA Foundation
(http://www.hsafoundation.com/) tools working group relates to the manner that
address spaces should be represented in DWARF.
HSA defines segments in which variables can be allocated. These are basically
the same as the address
