public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: chris@seberino.org
To: Ian Lance Taylor <iant@google.com>
Cc: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: objdump for old ARM7TDMI (ARMv4T) showing instructions for 	newer architectures?!
Date: Wed, 17 Jun 2009 01:06:00 -0000	[thread overview]
Message-ID: <20090617005108.GD28761@seberino.org> (raw)
In-Reply-To: <m3fxdzya4l.fsf@google.com>

On Tue, Jun 16, 2009 at 05:30:50PM -0700, Ian Lance Taylor wrote:
> The binutils snapshots do have ARM support.  There is no separate
> multiarch version of the binutils.  What are you doing that makes you
> think that the snapshots don't have ARM support?

Thanks for chiming in.  I did a standard build from source and then tried to do...

objdump -D --target=binary -m arm7tdmi foo

for some file foo and got this for the output...


foo:     file format binary

./objdump: Can't use supplied machine arm7tdmi


(-m armv4t gave "./objdump: Can't use supplied machine armv4t")

These worked in Ubuntu's objdump when I installed what Ubuntu calls their multiarch version of
binutils.

cs

  reply	other threads:[~2009-06-17  0:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 17:59 chris
2009-06-16 14:21 ` Nick Clifton
2009-06-16 15:41   ` Richard Earnshaw
2009-06-16 15:48     ` Nick Clifton
2009-06-16 15:51   ` Paul Brook
2009-06-16 16:24     ` Nick Clifton
2009-06-16 17:26       ` Paul Brook
2009-06-17  0:31   ` chris
2009-06-17  0:51     ` Ian Lance Taylor
2009-06-17  1:06       ` chris [this message]
2009-06-17  6:10         ` Ian Lance Taylor
2009-06-17  7:51           ` chris
2009-06-17 15:34         ` Dave Korn
2009-06-18  0:44     ` Minor inconsistent behaviors with objdump wondering about chris
2009-06-18 10:48       ` Nick Clifton
2009-06-18 20:19         ` chris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090617005108.GD28761@seberino.org \
    --to=chris@seberino.org \
    --cc=binutils@sourceware.org \
    --cc=iant@google.com \
    --cc=nickc@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).