From: Grant Edwards <grant.b.edwards@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: 32-bit host vs 64-bit host
Date: Tue, 25 Feb 2014 21:00:00 -0000 [thread overview]
Message-ID: <lej087$ah1$1@ger.gmane.org> (raw)
In-Reply-To: <20140225134757.f955220426e7925665b5897d8ef6e12e.7871ca77e8.wbe@email02.secureserver.net>
On 2014-02-25, <roman@kolesnikov.mobi> <roman@kolesnikov.mobi> wrote:
>>What sort of differences did you find?
>
> I could not compile the standard c library with the 32 bit toolchain on
> a 64 bit host, when the same library would build fine on the 32 bit
> host. I have ran into this issue many times during the second stage of
> the toolchain build on a 64 bit host. Same gcc/glibc sources would
> compile on a 32 bit host but would fail on a 64 bit.
Ah, I see. I suspect that has something to do with missing 32-bit
compatibility libraries. That's not really what I'm asking about.
I've got a 32-bit toolchain which has been in use for some time on
both 32-bit and 64-bit hosts -- everything works fine.
The last of the 32-bit machines in the development group was just
changed over to 64-bit. Now everybody is running 64-bit development
machines. I'm trying to decide how much testing and verification would
be needed if/when we rebuild the exact same toolchain as a 64-bit
hosted application.
For a naively written compiler (e.g. all of the one's I've
written/worked on), I would expect the exact same object code to be
emitted regardless of the word-size of the host. However, gcc is far
from "naive" and I wouldn't put it past the developers to write
optimizer code that actually generates different output when the
host's native word size changes.
One of these days, I'll build a toolchain on a 64-bit host and
actually compare some target program binaries to see if anything
changes...
--
Grant Edwards grant.b.edwards Yow! Now I'm concentrating
at on a specific tank battle
gmail.com toward the end of World
War II!
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-02-25 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 20:48 roman
2014-02-25 21:00 ` Grant Edwards [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-25 19:59 roman
2014-02-25 20:32 ` Grant Edwards
2014-02-24 21:27 Grant Edwards
2014-02-25 2:59 ` Ralf Corsepius
2014-03-02 2:00 ` Bill Pringlemeir
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='lej087$ah1$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=crossgcc@sourceware.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).