Displaying 2 results from an estimated 2 matches for "segment_selector_size".
2020 Mar 10
2
DWARF .debug_aranges data objects and address spaces
...r data covered
> by some entry owned by the corresponding compilation unit, followed by the
> non-zero length of that range
As such llvm is doing nothing generally wrong by emitting aranges for data
objects.
- llvm unconditionally sets the `.debug_aranges.segment_selector_size` to
zero[3]. GCC does this too. I think this is a bug if the target can have
overlapping ranges due to multiple code/data address spaces as in my case
of a Harvard machine.
As far as I can tell, the only upstream backend that is of a similar
configuration is AVR. I can reproduce...
2020 Mar 16
4
DWARF .debug_aranges data objects and address spaces
On Mon, Mar 16, 2020 at 9:31 AM Robinson, Paul <paul.robinson at sony.com>
wrote:
> With AVR being affected, upstreaming a patch to put segment selectors into
> .debug_aranges becomes completely reasonable. There would likely want to
> be a target hook somewhere to return a value saying what size to use, with
> the default implementation returning zero.
>
*nod* something