From: "Arati Dikey" <AratiD@kpit.com>
To: <binutils@sources.redhat.com>
Subject: sh-coff-objdump cannot disassemble DSP instructions
Date: Fri, 11 Jan 2002 09:25:00 -0000 [thread overview]
Message-ID: <97AA06615400F34AB695F23CE3D42E9148817C@sohm.kpit.com> (raw)
hi !
The sh-coff-objdump cannot disassemble DSP instructions
while the sh-elf-objdump does so. It simply interprets them as data
(.word)
After digging thru' the source code, I think that
this is because the assembler (sh-coff-as)
stores the bfd architecture as 'sh' and not 'sh-dsp' (arch =
bfd_arch_sh , machine = 0).
The 'static int sh_dsp' in tc-sh.c is set when -dsp option is given to
assembler.
How do I store this value in the bfd info ?
I have read the BFD manual but am still not sure
how and where to make modifications in the bfd backend.
Any help/guidance on this will be greatly appreciated.
Regards,
Arati Dikey
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Free download and free European support of GNU tool
chain (GNUSH v0101) for Hitachi's SH Series
Read more at http://www.kpit.com/products/support.htm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2002-01-11 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 9:25 Arati Dikey [this message]
2002-01-15 7:50 ` Nick Clifton
2002-06-14 9:11 ` Joern Rennecke
2002-01-15 23:31 Arati Dikey
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=97AA06615400F34AB695F23CE3D42E9148817C@sohm.kpit.com \
--to=aratid@kpit.com \
--cc=binutils@sources.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).