From: hjl@lucon.org (H.J. Lu)
To: ian@zembu.com (Ian Lance Taylor)
Cc: binutils@sourceware.cygnus.com
Subject: Re: Variable page size for ELF
Date: Sat, 10 Jul 1999 20:47:00 -0000 [thread overview]
Message-ID: <19990711034758.0B58C57B9@ocean.lucon.org> (raw)
In-Reply-To: <19990711024302.1424.qmail@daffy.airs.com>
>
> Date: Sat, 10 Jul 1999 19:24:37 -0700 (PDT)
> From: hjl@lucon.org (H.J. Lu)
>
> I got a request to support variable page size for ELF. It turned out
> not too hard to implement. Is that interesting to anyone? Should I
> send in my patch which adds "--page-size SIZE" to ld?
>
> It's hard for me to imagine an application for that. However, if
> there is some reason that it is useful, in a way that can not be
> handled by simply changing the linker script, then I have no objection
The problem is get_elf_backend_data (abfd)->maxpagesize in BFD and
MAXPAGESIZE in linker script. I did
1. Add functions to get/set get_elf_backend_data (abfd)->maxpagesize.
2. Made MAXPAGESIZE in linker script a variable.
Now the ELF linker script has
MAXPAGESIZE != 0 ? MAXPAGESIZE : ${MAXPAGESIZE}
in place of ${MAXPAGESIZE}.
> to such an option. At first glance it seems like anything you can do
> by changing the page size you can do by changing the linker script,
> using the PHDRS option.
>
How does PHDRS work?
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1999-07-10 20:47 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 [this message]
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
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=19990711034758.0B58C57B9@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--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).