From: Rick Mann <rmann@latencyzero.com>
To: gcc-help@gcc.gnu.org
Subject: More info: Binary built on different platforms with exact same tools different?
Date: Tue, 18 Dec 2007 00:54:00 -0000 [thread overview]
Message-ID: <D3994AA4-696E-4099-96BC-D2B7B533C7C1@latencyzero.com> (raw)
In-Reply-To: <5A2671EC-48B9-4492-A1E1-F346CE6811CC@latencyzero.com>
On Dec 17, 2007, at 4:43 PM, Rick Mann wrote:
> Hi. I've built an xscale-elf toolchain from gcc-4.2.2,
> binutils-2.17, newlib-1.15.0. I've used the exact same build
> procedure on both Mac OS X 10.5 (gcc-4.0.1-based) and Cygwin (gcc
> 3.4-based).
>
> Then I built our code and stripped the resulting binary with objcopy
> on each platform.
>
> Both binaries seem to run the same.
>
> However, cmp shows many differences between the two resulting
> binaries. Here are a few:
>
> $ cmp -l ~/h h | head -10
> 77 21 63
> 81 32 74
> 85 27 71
> 97 370 220
> 98 162 163
> 101 134 364
> 105 134 364
> 141 4 15
> 143 55 240
> 144 345 341
>
>
> Are these differences something to worry about?
I've disassembled the .elf files, and here are some of the differences:
Mac OS X:
8000804c <loop>:
8000804c: eb00a933 bl 80032520 <_init>
80008050: eb000c3c bl 8000b148 <main>
80008054: eb00a939 bl 80032540 <_fini>
80008058: eaffffe8 b 80008000 <//.>
8000805c: e89da800 ldmia sp, {fp, sp, pc}
...
80008060 <bss_start>:
80008060: 80047390 mulhi r4, r0, r3
80008064 <bss_end>:
80008064: 803a51f4 ldrhisht r5, [sl], -r4
Cygwin:
8000804c <loop>:
8000804c: eb00a911 bl 80032498 <_init>
80008050: eb000c1a bl 8000b0c0 <main>
80008054: eb00a917 bl 800324b8 <_fini>
80008058: eaffffe8 b 80008000 <//.>
8000805c: e89da800 ldmia sp, {fp, sp, pc}
...
80008060 <bss_start>:
80008060: 800472f8 strhid r7, [r4], -r8
80008064 <bss_end>:
80008064: 803a515c eorhis r5, sl, ip, asr r1
Some functions are placed in different order, too.
I'm trying to ensure that all our developers build identical binaries.
TIA,
--
Rick
next prev parent reply other threads:[~2007-12-18 0:54 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 ` Rick Mann [this message]
2007-12-18 0:59 ` More info: " NightStrike
2007-12-18 1:05 ` Rick Mann
2007-12-18 1:11 ` NightStrike
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=D3994AA4-696E-4099-96BC-D2B7B533C7C1@latencyzero.com \
--to=rmann@latencyzero.com \
--cc=gcc-help@gcc.gnu.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).