public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Dugger <n0ano@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ILP32 support?
Date: Tue, 22 Feb 2000 23:01:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678204958@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204954@msgid-missing>

Also, there would have to be some changes to the kernel.  This would
create ELF64 processes that have to live within the first 4G of
memory.  We already support 32-bit processes but some kernel changes
would be required to identify this new entity.

On Tue, Feb 22, 2000 at 03:08:54PM -0800, David Mosberger wrote:
> >>>>> On Tue, 22 Feb 2000 14:21:14 -0800, "Vadim Furman" <vadimf@mainsoft.com> said:
> 
>   Vadim> Are there any plans to support ILP32 mode?  Vadim Furman
> 
> No.  So far, nobody has felt that the (small) benefits of ILP32 are
> worth its trouble.  No kernel mods would be required, but you'd have
> to create a completely new user-level environment (new compiler, new
> header files, all libraries would have to be recompiled with ILP32
> mode, etc.).
> 
> 	--david
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@valinux.com
Ph: 303/938-9838



  reply	other threads:[~2000-02-22 23:01 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 [this message]
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
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-105590678204958@msgid-missing \
    --to=n0ano@valinux.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