Re: [Dwarf-Discuss] How to represent address space information in DWARF

2016-07-28 Thread Todd Allen
space >instance can be accessed when given a flat address that maps to the group >or private segments. It appears both gdb and lldb provide this. > FWIW, the use of DW_AT_address_class on pointer & reference times also is how Nvidia's CUDA compiler describes its

Re: [Dwarf-Discuss] Some DWARFv5 draft feedback

2016-12-01 Thread Todd Allen
ed DW_AT_encoding attributes directly on DW_TAG_enumeration_type to indicate the underlying signedness. Ada never was truly supported, so we just viewed it as part of the Ada support we'd defined. -- Todd Allen Concurrent Computer Corporation ___ Dwa

Re: [Dwarf-Discuss] Use of Location Description operations in DWARF Expressions?

2020-03-23 Thread Todd Allen via Dwarf-Discuss
y. It think it feels a little blurry only because locdescs came first, and then we co-opted them for DWARF expressions, and restricted the use of certain operators in that case. And then it eventually changed into what we have now. But a lot of us remember the history, which creates that blur. -

Re: [Dwarf-Discuss] Segment selectors for Harvard architectures

2020-03-23 Thread Todd Allen via Dwarf-Discuss
t; proposal or as a wiki entry. > > Thanks, > --paulr > > _______ > Dwarf-Discuss mailing list > Dwarf-Discuss@lists.dwarfstd.org > http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org -- Todd Allen Concurrent Real-Time ___ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org

Re: [Dwarf-Discuss] modeling different address spaces

2020-07-16 Thread Todd Allen via Dwarf-Discuss
ounds pretty close. I'm a bit >thrown off by the example, though. > > > >Thanks, > >Markus. > -- Todd Allen Concurrent Real-Time ___ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org

Re: [Dwarf-Discuss] string reduction techniques

2021-11-01 Thread Todd Allen via Dwarf-Discuss
Dave, If I understand right: The space saving you're expecting is the near-elimination of DW_AT_name strings. If they are only simple names like "T" and "int", they can be placed into the string table once each, and it should be very small. But you're expecting the DW_AT_linkage_name attributes

Re: [Dwarf-Discuss] string reduction techniques

2021-11-07 Thread Todd Allen via Dwarf-Discuss
dwarf-discuss-dwarfstd.org > > ___ > Dwarf-Discuss mailing list > [7]Dwarf-Discuss@lists.dwarfstd.org > [8]http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org > > References > >Visible links >

Re: [Dwarf-Discuss] [EXTERNAL] - RE: Multiple floating point types with the same size but different encodings

2022-01-25 Thread Todd Allen via Dwarf-Discuss
and a mention of any major peculiarities (e.g. skewed bias, inf/nan unsupported, etc.). -- Todd Allen Concurrent Real-Time ___ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org

Re: [Dwarf-Discuss] EXTERNAL: Corner-cases with bitfields

2022-05-06 Thread Todd Allen via Dwarf-Discuss
'm wondering if that impact is indirect: that is, the presence of this 0-width bit field changes an attribute of the next field, and that attribute is responsible for difference in the behavior. If so, is there any way other than a 0-width bit field to cause the same behavior? This might be another c

Re: [Dwarf-Discuss] EXTERNAL: Corner-cases with bitfields

2022-05-09 Thread Todd Allen via Dwarf-Discuss
On Mon, May 09, 2022 at 04:09:59PM -0700, Michael Eager wrote: > On 5/9/22 16:00, Todd Allen via Dwarf-Discuss wrote: > > I suppose, if you didn't want to submit an issue, another solution would be > > to > > require the necessary tags & attributes in the ABI itself

Re: [Dwarf-Discuss] EXTERNAL: Corner-cases with bitfields

2022-05-09 Thread Todd Allen via Dwarf-Discuss
xpect ABI documents to provide things like register values, CFI initial values, and some more esoteric stuff (augmentations, non-standard endianity & isa). An ABI that required descriptions in ABI-specific situations like these two seems reasonable to me. And it places no burden on compilers for other ABI's. -- Todd Allen Concurrent Real-Time ___ Dwarf-Discuss mailing list Dwarf-Discuss@lists.dwarfstd.org http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org

Re: [Dwarf-discuss] EXTERNAL: Re: ISSUE: tensor types. V3

2023-04-21 Thread Todd Allen via Dwarf-discuss
certain flavors of casts? (Those were the differences I spotted in that table.) This doesn't seem terribly compelling. But if others think it is, maybe this should be broken up into distinct features instead of a lumpy enum? -- Todd Allen Concurrent Real-Time -- Dwarf-discuss mailing list Dwarf-discuss@lists.dwarfstd.org https://lists.dwarfstd.org/mailman/listinfo/dwarf-discuss

Re: [Dwarf-discuss] ISSUE: tensor types. V3

2023-04-24 Thread Todd Allen via Dwarf-discuss
On 4/21/23 16:31, Ben Woodard via Dwarf-discuss wrote: >> >>>     Insert the following paragraph between the first paragraph of >>>     normative text describing DW_TAG_array_type and the second >>> paragraph >>>     dealing with multidimensional ordering. >>> >>>

Re: [Dwarf-discuss] ISSUE: tensor types. V3

2023-04-24 Thread Todd Allen via Dwarf-discuss
On 4/24/23 13:27, Ben Woodard via Dwarf-discuss wrote: > >> As for NEON vs. SVE, is there a need to differentiate them?  And can it >> not be done by shape of the type? > > That one continues to be hard. ARM processors that support SVE also have > NEON registers which like the Intel SSE MMX AVX