This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: What does--enable-64-bit-bfd mean anyway? Thinko in bfd-in.h?
- From: Alan Modra <amodra at bigpond dot net dot au>
- To: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Cc: "binutils at sourceware dot org" <binutils at sourceware dot org>
- Date: Tue, 19 May 2009 00:10:27 +0930
- Subject: Re: What does--enable-64-bit-bfd mean anyway? Thinko in bfd-in.h?
- References: <4A116DD5.3060208@gmail.com>
On Mon, May 18, 2009 at 03:16:53PM +0100, Dave Korn wrote:
> This looks like a thinko to me. Surely the size of a VMA and thus the size
> used to print it out in the dump fields should depend on the object file
> format in question, or perhaps the target, but certainly not on host
> characteristics?
No. A bfd_vma must be at least 64 bits if any target is 64-bit (the
main one or others selected by --enable-targets), or if
--enable-64-bit-bfd. A bfd_vma may also be 64 bits if the host is
64-bit (when unsigned long is 64-bit).
Printing a bfd_vma is a separate question. See bfd.c:bfd_fprintf_vma.
--
Alan Modra
Australia Development Lab, IBM