From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3816 invoked by alias); 27 Apr 2007 14:54:08 -0000 Received: (qmail 3805 invoked by uid 22791); 27 Apr 2007 14:54:06 -0000 X-Spam-Check-By: sourceware.org Received: from omta02sl.mx.bigpond.com (HELO omta02sl.mx.bigpond.com) (144.140.93.154) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 27 Apr 2007 15:53:54 +0100 Received: from oaamta02sl.mx.bigpond.com ([144.136.165.71]) by omta02sl.mx.bigpond.com with ESMTP id <20070427145351.POBQ10557.omta02sl.mx.bigpond.com@oaamta02sl.mx.bigpond.com>; Fri, 27 Apr 2007 14:53:51 +0000 Received: from bubble.grove.modra.org ([144.136.165.71]) by oaamta02sl.mx.bigpond.com with ESMTP id <20070427145350.SKDB19327.oaamta02sl.mx.bigpond.com@bubble.grove.modra.org>; Fri, 27 Apr 2007 14:53:50 +0000 Received: by bubble.grove.modra.org (Postfix, from userid 500) id A08F0241C37; Sat, 28 Apr 2007 00:23:50 +0930 (CST) Date: Fri, 27 Apr 2007 16:26:00 -0000 From: Alan Modra To: Kai Tietz Cc: binutils@sourceware.org Subject: Re: PATCH: Little endian target "binary_little" Message-ID: <20070427145350.GA13293@bubble.grove.modra.org> Mail-Followup-To: Kai Tietz , binutils@sourceware.org References: <20070427133906.GB11603@bubble.grove.modra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00363.txt.bz2 On Fri, Apr 27, 2007 at 03:54:14PM +0200, Kai Tietz wrote: > Alan Modra 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