public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: <roman@kolesnikov.mobi>
To: "Grant Edwards" <grant.b.edwards@gmail.com>, crossgcc@sourceware.org
Subject: RE: 32-bit host vs 64-bit host
Date: Tue, 25 Feb 2014 19:59:00 -0000	[thread overview]
Message-ID: <20140225125900.f955220426e7925665b5897d8ef6e12e.1e150ad80c.wbe@email02.secureserver.net> (raw)


Hi Grant,

I found the difference in building the libraries and file systems.
Making 32 bit chroot on 64 bit system was an extra nuisance.

Roman



-------- Original Message --------
Subject: 32-bit host vs 64-bit host
From: Grant Edwards <grant.b.edwards@gmail.com>
Date: Mon, February 24, 2014 2:26 pm
To: crossgcc@sourceware.org

Let's say I build two copies of the "same" toolchain: one on a 32-bit
(i686) host and the other on a 64-bit (amd64) host: both are using the
same configuration, same sources files, for the same target (e.g. ARM).

Would you expect the two toolchains to produce identical code when
given identical sources?

Or are there certain optimizations or transformations that differ
depend on the _host_ machine word-size or architecture?

For example: for the past few years you've been building an embedded
linux linux system for an ARM9 target using a 32-bit hosted toolchain.
How much of a risk is there if you move development to a 64-bit host
and rebuild your toolchains as 64-bit apps?

[Yes, I know that if you have 32-bit compatibility libraries you can
continue to use the existing 32-bit toolchain binaries.]

-- 
Grant Edwards grant.b.edwards Yow! Make me look like
 at LINDA RONSTADT again!!
 gmail.com 


--
For unsubscribe information see http://sourceware.org/lists.html#faq

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2014-02-25 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 19:59 roman [this message]
2014-02-25 20:32 ` Grant Edwards
  -- strict thread matches above, loose matches on Subject: below --
2014-02-25 20:48 roman
2014-02-25 21:00 ` 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=20140225125900.f955220426e7925665b5897d8ef6e12e.1e150ad80c.wbe@email02.secureserver.net \
    --to=roman@kolesnikov.mobi \
    --cc=crossgcc@sourceware.org \
    --cc=grant.b.edwards@gmail.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).