nyone who feels
> moved to provide padding has to re-invent the wheel), feel free to write a
> counter-proposal removing the existing mentions.
>
> --paulr
>
>
>
> *From:* David Blaikie
> *Sent:* Tuesday, January 30, 2024 6:01 PM
> *To:* Robinson, Paul
> *Cc:* dwarf-discuss
to provide padding has to re-invent the wheel), feel free to write a
counter-proposal removing the existing mentions.
--paulr
From: David Blaikie
Sent: Tuesday, January 30, 2024 6:01 PM
To: Robinson, Paul
Cc: dwarf-discuss@lists.dwarfstd.org
Subject: Re: [Dwarf-discuss] Proposal: Allow padding
Is anyone actually using this? In my experience linkers are generally
concatenating these sections together with no extra padding/alignment.
I'd rather not spec something that's not used/needed. I'm happy for
consumers to be improved in the face of degenerate entries that might be
created for
On 1/19/24 06:51, Robinson, Paul via Dwarf-discuss wrote:
Couldn't the abbrev table simply be padded with 0 bytes?
Hmmm... that would appear to a dumper as a series of zero-length tables,
I suppose? Would look funny in a dump but it could work. And would be a
lot simpler for the producer of
> > ### .debug_abbrev
> >
> > In Section 7.5.3 "Abbreviations Tables" (p.207), at the end of the
> section, add a new non-normative paragraph:
> >
> > *This table may be padded by adding an unused abbreviation entry. The
> minimum number of bytes in an abbreviation entry is four (abbreviation
>
> ### .debug_abbrev
>
> In Section 7.5.3 "Abbreviations Tables" (p.207), at the end of the section,
> add a new non-normative paragraph:
>
> *This table may be padded by adding an unused abbreviation entry. The minimum
> number of bytes in an abbreviation entry is four (abbreviation number,
This is Issue 240118.1.
https://dwarfstd.org/issues/240118.1.html
-cary
On Thu, Jan 18, 2024 at 11:08 AM Robinson, Paul via Dwarf-discuss
wrote:
>
> # Allow padding in all tables
>
> Enhancement; multiple sections.
>
> ## Background
>
> Issue 230329.1 requires all tables to be contiguous.
# Allow padding in all tables
Enhancement; multiple sections.
## Background
Issue 230329.1 requires all tables to be contiguous. During the discussion of
that issue, the question came up of whether all tables allowed padding, so that
contiguous concatenated contributions could be aligned
