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: Sun, 11 Jul 1999 10:38:00 -0000 [thread overview]
Message-ID: <19990711173805.D8E9D57BA@ocean.lucon.org> (raw)
In-Reply-To: <19990711151244.1933.qmail@daffy.airs.com>
> Merely changing the linker script is not a terribly useful feature,
> since people can already change it anyhow. The interesting new
> feature here is changing the use of maxpagesize in the backend data
> structure. However, the only interesting use of the backend
> maxpagesize is to set up the program headers, and you can already do
> that using PHDRS in the linker script.
I took a look at PHDRS. It is not easy to get it right with alignment
by hand.
>
> So I don't see any new functionality in the --page-size option. Of
> course, if it is a useful shorthand, we should add it anyhow. But
> that is where I wonder what the application is, since I don't see that
> either.
I got the request from our IA64 people.
>
> By the way, MAXPAGESIZE should probably not be used as a symbol name
> in a linker script, because it is part of the user's name space.
> Something like __MAXPAGESIZE would be better.
>
MAXPAGESIZE is a variable in linker script just like SIZEOF_HEADER.
It shouldn't show up in executable.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1999-07-11 10:38 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 [this message]
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=19990711173805.D8E9D57BA@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).