public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: "Rick Mann" <rmann@latencyzero.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: More info: Binary built on different platforms with exact same tools different?
Date: Tue, 18 Dec 2007 01:11:00 -0000	[thread overview]
Message-ID: <b609cb3b0712171711j49bdee66vfc27f3a5673fa277@mail.gmail.com> (raw)
In-Reply-To: <DC26D3F3-A493-4D67-8667-F0AE522D9F86@latencyzero.com>

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.

  reply	other threads:[~2007-12-18  1:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18  0:43 Rick Mann
2007-12-18  0:54 ` More info: " Rick Mann
2007-12-18  0:59   ` NightStrike
2007-12-18  1:05     ` Rick Mann
2007-12-18  1:11       ` NightStrike [this message]
2007-12-18  1:15         ` Rick Mann
2007-12-18  6:25       ` Kaz Kylheku

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=b609cb3b0712171711j49bdee66vfc27f3a5673fa277@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=rmann@latencyzero.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).