[prev in list] [next in list] [prev in thread] [next in thread]
List: binutils
Subject: Re: dwarf2: pointer size vs address size
From: Nick Clifton <nickc () redhat ! com>
Date: 2006-06-28 9:19:12
Message-ID: 44A24990.9050700 () redhat ! com
[Download RAW message or body]
Hi DJ,
> In various places, we refer to "pointer size" to refer to things the
> dwarf2 spec calls "address size". Example: include/elf/dwarf.c has
> cu_pointer_size, and readelf prints "Pointer size:" for the address
> size given in compilation unit headers.
>
> On some platforms, the pointer size is not the same as the address
> size. Example: m16c has a 20 bit address space, but only 16 bit
> pointers, and we use 32 bit addresses in its dwarf information.
>
> To avoid confusion, would anyone object to renaming those things to
> say "address" instead of "pointer" ?
No objections, in fact definite encouragement.
> On a related note, readelf ignores this field when printing EH tables.
> It blindly assumes that EH addresses will be either 32 or 64 bit, and
> uses the machine type to decode it. Why?
Poor coding assumption.
Cheers
Nick
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic