From: Rick Mann <rmann@latencyzero.com>
To: gcc-help@gcc.gnu.org
Subject: Binary built on different platforms with exact same tools different?
Date: Tue, 18 Dec 2007 00:43:00 -0000 [thread overview]
Message-ID: <5A2671EC-48B9-4492-A1E1-F346CE6811CC@latencyzero.com> (raw)
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?
TIA,
Rick
next reply other threads:[~2007-12-18 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 0:43 Rick Mann [this message]
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
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=5A2671EC-48B9-4492-A1E1-F346CE6811CC@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).