Re: [Dwarf-Discuss] Segment selectors for the range list table.

Anyone know of any existing DWARF producers that use segmented addressing? Might be interesting to see how they're using the features. On Thu, Jul 16, 2020 at 9:30 AM Michael Eager wrote: > On 7/15/20 9:49 PM, David Blaikie wrote: > > > > > > On Wed, Jul 15, 2020 at 7:07 PM Michael Eager via

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On Thu, Jul 16, 2020 at 6:35 PM Michael Eager wrote: > On 7/16/20 5:37 PM, David Blaikie wrote: > > > > > > On Thu, Jul 16, 2020 at 4:25 PM Michael Eager > > The language used to describe segmented addressing in DW_AT_segment > > reads to me like the same language used to describe segmented

[Dwarf-Discuss] modeling different address spaces

Hello, What would be the recommended way to model variables that are allocated to different address spaces? I found DW_OPT_xderef for dereferencing address-space qualified pointers but the resulting memory location description wouldn’t have an address-space qualifier. I found

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On 7/15/20 9:49 PM, David Blaikie wrote: On Wed, Jul 15, 2020 at 7:07 PM Michael Eager via Dwarf-Discuss > wrote: Segmented addresses have been in the DWARF specification since Version 2   and AFAIK have not been changed since that time. 

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 2:23 AM, Metzger, Markus T via Dwarf-Discuss wrote: Hello, What would be the recommended way to model variables that are allocated to different address spaces? Can you describe the architecture a bit? I found DW_OPT_xderef for dereferencing address-space qualified pointers but

Re: [Dwarf-Discuss] modeling different address spaces

Markus, Michael, David, Xing, I always assumed that the segment support in DWARF was meant to be more general, and support architectures where there was no single flat memory, and so the segments were necessary for memory accesses. I personally have not dealt with any architectures where

Re: [Dwarf-Discuss] modeling different address spaces

> -Original Message- > From: Dwarf-Discuss On Behalf > Of Michael Eager via Dwarf-Discuss > Sent: Thursday, July 16, 2020 2:22 PM > To: John DelSignore ; todd.allen@concurrent- > rt.com; Metzger, Markus T > Cc: dwarf-discuss@lists.dwarfstd.org; Tye, Tony > Subject: Re:

Re: [Dwarf-Discuss] modeling different address spaces

FYI, Tony Tye and his team at AMD created a DWARF Proposal for heterogeneous debugging, which is generally useful but required to debug optimized code for GPUs. It directly addresses the issue of how to model different address spaces and makes location descriptions first-class objects that can

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 10:06 AM, Todd Allen via Dwarf-Discuss wrote: Markus, Michael, David, Xing, I always assumed that the segment support in DWARF was meant to be more general, and support architectures where there was no single flat memory, and so the segments were necessary for memory accesses. I

Re: [Dwarf-Discuss] modeling different address spaces

(resending, this time without dropping the list from the cc: grump grump) > -Original Message- > From: Dwarf-Discuss On Behalf > Of Michael Eager via Dwarf-Discuss > Sent: Thursday, July 16, 2020 2:12 PM > To: todd.al...@concurrent-rt.com; Metzger, Markus T > > Cc:

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 10:26 AM, John DelSignore via Dwarf-Discuss wrote: FYI, Tony Tye and his team at AMD created a DWARF Proposal for heterogeneous debugging, which is generally useful but required to debug optimized code for GPUs. It directly addresses the issue of how to model different address

Re: [Dwarf-Discuss] modeling different address spaces

On Thu, Jul 16, 2020 at 11:41 AM Robinson, Paul via Dwarf-Discuss < dwarf-discuss@lists.dwarfstd.org> wrote: > (resending, this time without dropping the list from the cc: grump grump) > > > -Original Message- > > From: Dwarf-Discuss On Behalf > > Of Michael Eager via Dwarf-Discuss > >

Re: [Dwarf-Discuss] modeling different address spaces

On 7/16/20 11:51 AM, David Blaikie wrote: On Thu, Jul 16, 2020 at 11:41 AM Robinson, Paul via Dwarf-Discuss The example that most often comes up is Harvard architectures.  As it happens, I think it's nearly always obvious from context whether a given address is data-segment or

Re: [Dwarf-Discuss] modeling different address spaces

On Thu, Jul 16, 2020 at 12:55 PM Michael Eager wrote: > On 7/16/20 11:51 AM, David Blaikie wrote: > > > > > > On Thu, Jul 16, 2020 at 11:41 AM Robinson, Paul via Dwarf-Discuss > > The example that most often comes up is Harvard architectures. As it > > happens, I think it's nearly

Re: [Dwarf-Discuss] Segment selectors for the range list table.

Perhaps it's more like Paul was postulating - that the spec assumes code is in a code segment/doesn't need to be clarified. (but that gets a bit confused in debug_aranges - if it only is meant to contain code (not data), why does it need a segment selector - and also in the DIEs - if code is

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On Thu, Jul 16, 2020 at 1:07 PM Michael Eager wrote: > > Perhaps it's more like Paul was postulating - that the spec assumes code > > is in a code segment/doesn't need to be clarified. (but that gets a bit > > confused in debug_aranges - if it only is meant to contain code (not > > data), why

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On 7/16/20 1:36 PM, David Blaikie wrote: On Thu, Jul 16, 2020 at 1:07 PM Michael Eager > wrote: > Perhaps it's more like Paul was postulating - that the spec assumes code > is in a code segment/doesn't need to be clarified. (but that gets a bit

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On Thu, Jul 16, 2020 at 2:05 PM Michael Eager wrote: > On 7/16/20 1:36 PM, David Blaikie wrote: > > > > > > On Thu, Jul 16, 2020 at 1:07 PM Michael Eager > > wrote: > > > > > Perhaps it's more like Paul was postulating - that the spec > > assumes code > >

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On 7/16/20 2:57 PM, David Blaikie wrote: On Thu, Jul 16, 2020 at 2:05 PM Michael Eager You appear to be starting with a counterfactual premise and using that to postulate a problem where none exists. Sorry - I seem to be misunderstanding what you mean by "there are no restrictions

Re: [Dwarf-Discuss] Segment selectors for the range list table.

On Thu, Jul 16, 2020 at 4:25 PM Michael Eager wrote: > On 7/16/20 2:57 PM, David Blaikie wrote: > > > > > > On Thu, Jul 16, 2020 at 2:05 PM Michael Eager > > > You appear to be starting with a counterfactual premise and using > that > > to postulate a problem where none exists. > > > >