From: Nick Clifton <nickc@redhat.com>
To: Андрей <andynvkz@mail.ru>, binutils@sourceware.org
Subject: Re: objdump
Date: Thu, 1 Feb 2024 13:03:06 +0000 [thread overview]
Message-ID: <dcef4043-c631-4134-9800-31729bebc934@redhat.com> (raw)
In-Reply-To: <1706571900.419402903@f140.i.mail.ru>
Hi Андрей,
> I'm trying to disassemble the csky processor code, the processor is 32-bit, with 32-bit V2 instructions, but objdump outputs data and code as 16-bit, how can I force it to
> output in 32-bit?
You *might* be able to achieve this using objdump's -m command line option.
For example:
objdump -m csky:ck801 -d <file>
The list of csky architecture types supported by objdump are listed in its --help output.
Cheers
Nick
next prev parent reply other threads:[~2024-02-01 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 23:45 objdump Андрей
2024-02-01 13:03 ` Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-19 10:49 objdump clint
[not found] <20010902153028.A19762@fuchs.offl.uni-jena.de>
2001-09-05 9:30 ` objdump Nick Clifton
2000-05-28 11:43 Objdump Nick Clifton
2000-05-28 5:16 Objdump n3d
2000-05-27 13:10 Objdump n3d
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=dcef4043-c631-4134-9800-31729bebc934@redhat.com \
--to=nickc@redhat.com \
--cc=andynvkz@mail.ru \
--cc=binutils@sourceware.org \
/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).