This is the mail archive of the
mailing list for the binutils project.
Re: objdump always displays LSbytes first irrespective of endianess of target
- From: Ian Lance Taylor <ian at wasabisystems dot com>
- To: Shekhar Divekar <shekhar at cradle dot com>
- Cc: binutils at sources dot redhat dot com
- Date: 14 Jan 2004 08:48:38 -0500
- Subject: Re: objdump always displays LSbytes first irrespective of endianess of target
- References: <1074076062.5431.34.camel@shekhar>
Shekhar Divekar <firstname.lastname@example.org> writes:
> I am working on a port of binutils with LITTLE ENDIAN target.
> In the dump I would like to see MSByte first as it is natural for
> little endian m/c. But objdump always displays LSbytes first
> irrespective of endianess of target. On further investigation I found
> out that this is because in objdump.c:disassemble_bytes 'bpc' is always
> initialized to 1, which results in check for 'display_endian' while
> producing the dump, useless.
What sources are you using? In the current sources, bpc is controlled
by info->bytes_per_chunk, and the disassembler is expected to set that
For example, a typical RISC target for which all instructions are 4
bytes would set info->bytes_per_chunk to 4 in the disassembler. See,