From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-30907-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 18872 invoked by alias); 18 Dec 2007 01:11:59 -0000
Received: (qmail 18858 invoked by uid 22791); 18 Dec 2007 01:11:58 -0000
X-Spam-Check-By: sourceware.org
Received: from nz-out-0506.google.com (HELO nz-out-0506.google.com) (64.233.162.234)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 18 Dec 2007 01:11:54 +0000
Received: by nz-out-0506.google.com with SMTP id i11so1198577nzh.26         for <gcc-help@gcc.gnu.org>; Mon, 17 Dec 2007 17:11:52 -0800 (PST)
Received: by 10.143.171.5 with SMTP id y5mr1379541wfo.73.1197940311792;         Mon, 17 Dec 2007 17:11:51 -0800 (PST)
Received: by 10.142.199.17 with HTTP; Mon, 17 Dec 2007 17:11:51 -0800 (PST)
Message-ID: <b609cb3b0712171711j49bdee66vfc27f3a5673fa277@mail.gmail.com>
Date: Tue, 18 Dec 2007 01:11:00 -0000
From: NightStrike <nightstrike@gmail.com>
To: "Rick Mann" <rmann@latencyzero.com>
Subject: Re: More info: Binary built on different platforms with exact same tools different?
Cc: gcc-help@gcc.gnu.org
In-Reply-To: <DC26D3F3-A493-4D67-8667-F0AE522D9F86@latencyzero.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5A2671EC-48B9-4492-A1E1-F346CE6811CC@latencyzero.com> 	 <D3994AA4-696E-4099-96BC-D2B7B533C7C1@latencyzero.com> 	 <b609cb3b0712171659x2339e0c8ya310986f0f2f9bbf@mail.gmail.com> 	 <DC26D3F3-A493-4D67-8667-F0AE522D9F86@latencyzero.com>
X-IsSubscribed: yes
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-help.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
X-SW-Source: 2007-12/txt/msg00326.txt.bz2

On 12/17/07, Rick Mann <rmann@latencyzero.com> wrote:
>
> On Dec 17, 2007, at 4:59 PM, NightStrike wrote:
>
> > Why would binaries on different platforms be identical?
>
> The toolchain on each host platform is built with identical steps,
> from the same source distro, targetting an embedded Xscale processor.
>
> The source code does not use any OS APIs, just some things in newlib
> (built as part of the toolchain).
>
> The resulting binary should, in theory, be identical, regardless of
> the host platform.

Ah, you are cross compiling.  I misunderstood.  So on both platforms,
you are building a cross compiler, gcc 4.2  You are then using that
cross compiler that you build on each platform to build your program,
and the resulting executable is different.

Hmm....  Interesting scenario.