From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] native ia64 32-bits compile & run on linux-ia64?
Date: Tue, 22 Jan 2002 19:02:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805914@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805893@msgid-missing>
I think one point that hasn't been made so far is that we actively
discourage supporting an ILP32 data model for IA-64 Linux to avoid
splitting ia64 linux into two different worlds (32-bit and 64-bit
world). If we supported ILP32, it's very likely that some ISVs will
decide to provide *only* 32-bit libraries, which could in turn force
other ISVs to stay with 32-bit just because they couldn't get the
pre-requisite 64-bit libraries. My understanding is that IRIX
suffered from this effect.
There are times where an ILP32 model would achieve slightly better
performance, but it's certainly not always the case and, in my
opinion, the potential performance benefit is not worth the cost of
having to maintain two data models (ILP32 and LP64). Note that the
cost is not just in developing, testing, and maintaining two versions
of each library, but also in added complexity for programmers.
--david
next prev parent reply other threads:[~2002-01-22 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 15:01 [Linux-ia64] native ia64 32-bits compile & run on linux-ia64? Francois-Xavier Kowalski
2002-01-21 15:49 ` n0ano
2002-01-21 17:07 ` Francois-Xavier Kowalski
2002-01-21 17:27 ` Jes Sorensen
2002-01-21 17:30 ` n0ano
2002-01-22 8:43 ` Francois-Xavier Kowalski
2002-01-22 19:02 ` David Mosberger [this message]
2002-01-22 19:37 ` Jes Sorensen
2002-01-23 11:27 ` Francois-Xavier Kowalski
2002-01-23 17:46 ` Boehm, Hans
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=marc-linux-ia64-105590698805914@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.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