From: Alan Modra <amodra@bigpond.net.au>
To: Kai Tietz <Kai.Tietz@onevision.com>
Cc: binutils@sourceware.org
Subject: Re: PATCH: Little endian target "binary_little"
Date: Fri, 27 Apr 2007 16:26:00 -0000 [thread overview]
Message-ID: <20070427145350.GA13293@bubble.grove.modra.org> (raw)
In-Reply-To: <OFA965FB52.99382EE9-ONC12572CA.004C09C4-C12572CA.004C60AD@onevision.de>
On Fri, Apr 27, 2007 at 03:54:14PM +0200, Kai Tietz wrote:
> Alan Modra <amodra@bigpond.net.au> wrote on 27.04.2007 15:39:06:
>
> > On Fri, Apr 27, 2007 at 10:39:37AM +0200, Kai Tietz wrote:
> > > I want to introduce an new internal default bfd target
> "binary_little".
> >
> > I don't see the sense in this. Where does the binary bfd backend use
> > its bfd_getx or bfd_putx functions?
>
> I was quested by H.J, that the windres tool should use bfd I/O instead of
> FILE I/O. Therefore it is necessary, that the binary format used for res
> output - using bfd_put_16, etc. - has a little endian equivalent.
No. Use bfd_putl16, bfd_putl32, bfd_putl64.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2007-04-27 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 14:43 Why aren't we consistent on displacement in x86 disassembler? H. J. Lu
2007-04-26 14:54 ` H. J. Lu
2007-04-26 15:54 ` Jan Beulich
2007-04-26 15:59 ` H. J. Lu
2007-04-26 16:05 ` Jan Beulich
2007-04-26 16:23 ` H. J. Lu
2007-04-26 16:31 ` Alan Modra
2007-04-26 17:19 ` H. J. Lu
2007-04-27 8:40 ` PATCH: PR binutils/4430: We aren't consistent on displacement in x86 disassembler H. J. Lu
2007-04-27 12:40 ` PATCH: Little endian target "binary_little" Kai Tietz
2007-04-27 13:54 ` Alan Modra
2007-04-27 14:54 ` Kai Tietz
2007-04-27 16:26 ` Alan Modra [this message]
2007-04-27 13:39 ` PATCH: PR binutils/4430: We aren't consistent on displacement in x86 disassembler Paul Brook
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=20070427145350.GA13293@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=Kai.Tietz@onevision.com \
--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).