Hi there! On 7/31/20 1:17 AM, Tye, Tony via Dwarf-Discuss wrote: > 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 address > spaces, registers, etc. Describing this situation with a DW_AT_address_class > on a source language variable is not possible as it provides a single address > space that applies to the variable as a whole. The concept of "address space" > is not available on the expression stack where a composite location > description is created. > > > > Instead, making address space a property of memory location descriptions and > making location descriptions a first-class concept on the expression stack > solves the problem in a general way and leads to other nice properties.
I am interesting in re-reading the document describing your changes, but the url that was pasted on the list before: https://llvm.org/docs/AMDGPUDwarfProposalForHeterogeneousDebugging.html is now returning "Not Found". Did the document move somewhere else? Pedro Alves _______________________________________________ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org