This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: v850-unknown-elf-objdump, can't disassemble for architecture unknown
- From: Bernd Jendrissek <berndj at prism dot co dot za>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: tmohr at s dot netic dot de, binutils at sources dot redhat dot com
- Date: Mon, 18 Jul 2005 14:54:55 +0200
- Subject: Re: v850-unknown-elf-objdump, can't disassemble for architecture unknown
- References: <200506132327.31457.tmohr@s.netic.de> <42AEB073.7040106@redhat.com> <20050614202915.GA22916@nevyn.them.org> <200506142328.34496.tmohr@s.netic.de> <20050614224039.GA27003@nevyn.them.org> <42AFE64C.5050305@redhat.com>
On Wed, Jun 15, 2005 at 09:26:52AM +0100, Nick Clifton wrote:
> >But maybe the GNU tools should accept EM_V800.
>
> It should, and so I am checking in the attached patch. With this
> applied I am able to disassemble the binary that Torsten sent, without
> having to modify it in any way.
>
> Torsten: Please note that this patch allows the binutils code to read
> binary files produced by the GreenHills toolchain. It does not make
> it produce binaries that are compatible with the GreenHills toolchain
> however. So if you use the GNU linker to create an executable it
> probably not be compatible with the GreenHills disassembler, debugger,
> etc. (I am assuming that GreenHills does not support the EM_V850
> machine number).
I can confirm that the GNU linker is *not* compatible with GHS binaries;
GHS objects use differently-numbered relocations, for one.
I gave up trying to get the two to interoperate when I found that ld
interprets relocations according to the first (??) input file's BFD,
instead of, say, translating all relocs to target-agnostic BFD ones
first, then linking, then rendering the leftover relocs according to the
*output* file BFD.
(I really needed just to link my poor-man's pthreads into an existing
project, but *wanted* to build it all with a GNU toolchain.)
--
Problems experienced downstream are symptoms of neglect upstream.
Upstream problems can only be solved upstream. - Ad Sparrius