[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ld x86-64 bug
From: |
Daniel Jacobowitz |
Subject: |
Re: ld x86-64 bug |
Date: |
Mon, 10 Feb 2003 15:33:44 -0500 |
User-agent: |
Mutt/1.5.1i |
On Mon, Feb 10, 2003 at 08:27:17PM +1030, Alan Modra wrote:
> On Mon, Jan 27, 2003 at 09:51:58PM +0100, Jan Stoess wrote:
> > 0 .text 00000192 0000000000123456 0000000000123456 00023456
> > 2**6
> > Looking at the 6th column, the file offset of the text section is
> > equal to the maximum of the LMA of text section (Column 5) and
> > 0x100000; i tried several values for start_text in the Linker Script.
> > This makes the file unnecessarily big...
>
> This is a consequence of ld/emulparams/elf_x86_64.sh setting
> MAXPAGESIZE=0x100000. MAXPAGESIZE sets the maximum disk and memory
> page size that might be used by whatever operating system you're
> using. Demand paging of executables generally requires that
> vma % pagesize == file_offset % pagesize.
>
> If you want to save disk space you can reduce MAXPAGESIZE to a lower
> value such as 0x1000, which might be the maximum currently used by
> your operating system.
A question that's come up before: if you know the maximum page size
used by an operating system, does shrinking MAXPAGESIZE (as long as it
stays above that limit) impact the ABI? Or does it only impact
compatibility with some future potential OS which uses a larger page
size?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer