public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc 3.0 question: ILP32 mode ?
Date: Mon, 30 Jul 2001 22:36:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005959@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005928@msgid-missing>

>>>>> On 31 Jul 2001 00:06:48 +0200, Jes Sorensen <jes@sunsite.dk> said:

  Jose> Some code is just not worth cleaning up because it is too big,
  Jose> and will never require 64 bit addressing, but still useful to
  Jose> have in native mode, mostly because of the performance gap
  Jose> between ia32 and ILP32 which will moreover widen with the
  Jose> McKinley chip. Look at netscape, it has never been cleaned up,
  Jose> it was ported on linux alpha using the DEC/Compaq/(Intel now?)
  Jose> compiler in taso mode (32 bit pointers).

  Jes> Linux/Alpha's glibc doesn't support 32 bit pointers afaik.

Note that netscape doesn't/didn't get cleaned up for 64 bits because
Mozilla already *is* 64-bit clean.

I have yet to see a program that is worth running in natively yet not
worth cleaning up for 64 bits.

	--david


      parent reply	other threads:[~2001-07-30 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 19:50 [Linux-ia64] gcc 3.0 question: ILP32 mode ? Jose Luu
2001-07-26 20:18 ` Boehm, Hans
2001-07-26 20:19 ` Rich Altmaier
2001-07-26 22:42 ` Jose Luu
2001-07-26 23:32 ` Don Dugger
2001-07-30 22:06 ` Jes Sorensen
2001-07-30 22:15 ` Rik van Riel
2001-07-30 22:16 ` Christoph Hellwig
2001-07-30 22:36 ` David Mosberger [this message]

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-105590693005959@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