Bloated binaries following the use of AT(...) linker script command
Prasad B
bprasad@cs.arizona.edu
Tue Jun 16 03:11:00 GMT 2009
More information about the Binutils mailing list
Tue Jun 16 03:11:00 GMT 2009
- Previous message (by thread): Bloated binaries following the use of AT(...) linker script command
- Next message (by thread): Bloated binaries following the use of AT(...) linker script command
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Jun 15, 2009 at 7:17 PM, Alan Modra<amodra@bigpond.net.au> wrote: > Why are you specifying a 64-bit AT value for a 32-bit target? My > guess is that you have ld compiled with a 64-bit vma (either 64-bit > host, at least one 64-bit target, or --enable-64-bit-bfd) and have hit > some ld code that isn't 64-bit clean. Thanks Alan for the response. I changed the value to a 32-bit one and the problem persists. PHDRS { text PT_LOAD AT(0x81000000) FLAGS(7); /* RWX */ note PT_NOTE FLAGS(4); /* R__ */ } Entry point address: 0xc00050b0 Start of program headers: 52 (bytes into file) Start of section headers: 1069094904 (bytes into file) The binary referred to in the problem is linux kernel. thank you, Prasad.
- Previous message (by thread): Bloated binaries following the use of AT(...) linker script command
- Next message (by thread): Bloated binaries following the use of AT(...) linker script command
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list