This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: objdump's ARM instruction names messed up in latest versions?
- From: Daniel Jacobowitz <drow at false dot org>
- To: chris at seberino dot org
- Cc: binutils at sourceware dot org
- Date: Tue, 16 Jun 2009 13:45:04 -0400
- Subject: Re: objdump's ARM instruction names messed up in latest versions?
- References: <20090616173436.GA26934@seberino.org>
On Tue, Jun 16, 2009 at 10:34:36AM -0700, chris@seberino.org wrote:
> ARM has a weird way of naming instructions that was adhered to in objdump version
> 2.17 but seems to have gotten messed up in 2.19.1 (on Ubuntu 9.04 with
> 2.19.1-multiarch)
>
> I'm referring to the position of the "condition codes".
>
> For example, the ldrt instruction with an "eq" condition code should be named
> "ldreqt".
>
> The 2.19.1 version of objdump violates this ARM convention and puts all
> condition codes at the *end*...e.g. "ldrteq".
>
> What that intentional or is this a bug in latest objdump?
It's deliberate; ARM have changed their recommended syntax, to what is
called the "unified syntax". This is designed to be uniform between
ARM and Thumb-2 modes.
I don't know why that involved moving the condition codes around - it
may have been to make things more uniform.
You can use ".syntax unified" in assembly files to select the new
syntax.
--
Daniel Jacobowitz
CodeSourcery