public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@cygnus.com>
To: "H.J. Lu" <hjl@lucon.org>
Cc: ian@zembu.com, binutils@sourceware.cygnus.com
Subject: Re: Variable page size for ELF
Date: Sun, 11 Jul 1999 15:11:00 -0000	[thread overview]
Message-ID: <19990711151144.A23263@cygnus.com> (raw)
In-Reply-To: <19990711202251.0A49B57BA@ocean.lucon.org>

On Sun, Jul 11, 1999 at 01:22:51PM -0700, H.J. Lu wrote:
> 1. Some OSes do support variable page size. IRIX is one of them. But
> you need some way to tell the system what page size you want. It is
> possible that one day Linux will support variable page size on
> platforms where the hardware support is available.

What has this to do with the maximum architectural page size?
Which is what's supposed to be used in BFD.  That maximum is
specified by the IA64 spec as 64K.

> 2. IA32 has 4K page size. But we may want to use a different page size
> for IA32 binaries when run them under IA64.

No, you can't do that.  All sorts of existing programs will break,
and the whole point of such non-native emulation is to not break
old programs.

> 3. The page size of Linux/IA64 may change due to various reasons. It
> will be helpful to change page size via linker command line.

Again, no.  The value in BFD is the _maximum_ architectural page
size.  By arranging binaries this way, we free the operating system
to choose _any_ architecturally supported page size.


r~

  reply	other threads:[~1999-07-11 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-10 19:24 H.J. Lu
1999-07-10 19:44 ` Ian Lance Taylor
1999-07-10 20:47   ` H.J. Lu
1999-07-11  8:13     ` Ian Lance Taylor
1999-07-11 10:38       ` H.J. Lu
1999-07-11 13:02         ` Richard Henderson
1999-07-11 13:22           ` H.J. Lu
1999-07-11 15:11             ` Richard Henderson [this message]
1999-07-11 16:45         ` Ian Lance Taylor

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=19990711151144.A23263@cygnus.com \
    --to=rth@cygnus.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=hjl@lucon.org \
    --cc=ian@zembu.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).