[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/702] New: mipsel a.out always more than 64 kbyte
From: |
klaas dot de dot waal at philips dot com |
Subject: |
[Bug ld/702] New: mipsel a.out always more than 64 kbyte |
Date: |
1 Feb 2005 16:19:55 -0000 |
A small "hello world" program gives an executable of more than 64 kbyte when
linked with shared libraries. With binutils-2.14 the same "hello world" program
gives an executable of about 6 kbyte.
Looking at the result of the following command:
readelf -a a.out | grep LOAD
shows that the LOAD entries in Program Headers now have an alignment of 0x10000
(64 kbyte)
The same command on an a.out generated with binutils-2.14 shows alignment of
0x1000 (4 kbyte)
The bintutils-2.14.91 also generates big a.out with alignment of 64 kbyte.
This suggests that the alignment value correlates with the a.out size.
Curious: on a.out binaries of X86 the alignment is 0x1000 but the executable
size is less than 4 kbyte (with binutils-2.15, as found on FC3).
For mipsel cross-compilation, I use a cross-compilation toolchain generated with
Dan Kegel's crosstools with the following parameters:
- crosstools-0.38-rc37
- gcc-3.3.3
- glibc-2.3.2
- binutils-2.14, 2.14.91 or 2.15
- linux-2.4.18
--
Summary: mipsel a.out always more than 64 kbyte
Product: binutils
Version: 2.15
Status: NEW
Severity: normal
Priority: P2
Component: ld
AssignedTo: unassigned at sources dot redhat dot com
ReportedBy: klaas dot de dot waal at philips dot com
CC: bug-binutils at gnu dot org
GCC build triplet: i686-linux
GCC target triplet: mipsel-unknown-linux-gnu
http://sources.redhat.com/bugzilla/show_bug.cgi?id=702
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug ld/702] New: mipsel a.out always more than 64 kbyte,
klaas dot de dot waal at philips dot com <=