From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] ILP32 support?
Date: Wed, 23 Feb 2000 00:40:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678204961@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204954@msgid-missing>
>>>>> On Tue, 22 Feb 2000 16:11:53 -0800, "Vadim Furman" <vadimf@mainsoft.com> said:
Vadim> IMHO benefits of ILP32 are huge, since you can relatively
Vadim> simply port existing 32 apps to ia64 and in the same time
Vadim> enjoy the perfomance of the new chip.
If it's not a performance critical program, you might just as well
leave it an x86 binary and do no porting at all. If it's a
performance critical program, then it's probably worthwhile to make it
64-bit clean (which isn't hard) and get the benefit of wide arithmetic
and assurance that the program can deal with 64-bit files, address
spaces, and y2038 without any problem at all.
Vadim> Is it possible to force LP64 processes below 4G? Is there a
Vadim> compiler/linker switch to do so?
You can use a linker script to force things below 4GB. For mmap,
you'd need to change the kernel to push the mmap base below 4GB.
You'll be on your own though if you do this. All open source programs
I know of are 64-bit clean so the incentive for the open source
community to support ILP32 is very small.
--david
next prev parent reply other threads:[~2000-02-23 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-22 22:21 [Linux-ia64] ILP32 support? Vadim Furman
2000-02-22 23:01 ` Don Dugger
2000-02-22 23:08 ` David Mosberger
2000-02-23 0:02 ` David Mosberger
2000-02-23 0:11 ` Vadim Furman
2000-02-23 0:40 ` David Mosberger [this message]
2000-02-23 0:47 ` Rich Altmaier
2000-02-23 1:34 ` Dan Pop
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-105590678204961@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