Re: RFC: Change in dwarf2dbg using sizeof_offset

[Alan Modra <amodra at bigpond dot net dot au>]

On Wed, Jul 30, 2008 at 10:08:57AM -0400, Daniel Jacobowitz wrote:
> On Wed, Jul 30, 2008 at 05:59:23PM +0930, Alan Modra wrote:
> > I don't think either of these are bugs, but it is a little strange
> > that we don't use the 64-bit offsets for 64-bit targets since that
> > means we can't have a .debug_info section larger than 4G.
> 
> I am pretty sure that is deliberate.  The 64-bit size is wasteful;
> only rare cases need 64-bit offsets in debug info.  I wouldn't be
> opposed to an option, but I don't think it's a good idea to increase
> the size of debug info so much (I'd guess 20-25% depending on what
> offsets you're talking about changing).

The .debug_aranges change will increase its size by 12 bytes per
compilation unti.  The .debug_info change increases its size by 4
bytes per compilation unit.  I don't see this as a big deal.

We aren't talking about changing anything to do with target
addresses/offsets.  They are already 64-bit for a 64-bit target even
in the current 32-bit dwarf .debug_aranges.

-- 
Alan Modra
Australia Development Lab, IBM