On Sat, Jan 07, 2006 at 07:56:22PM -0800, Mitchell Blank Jr took 0 lines to write:
> Kurt Wall wrote:
> > text data bss dec hex filename
> > 2577982 462352 479920 3520254 35b6fe vmlinux.344.NO_OPT
> > 2620255 462336 479984 3562575 365c4f vmlinux.442.NO_OPT
> > 2326785 462352 479920 3269057 31e1c1 vmlinux.344.OPT
> > 2227294 502680 479984 3209958 30fae6 vmlinux.442.OPT
>
> And idea what's up with the .data size there? The first three are almost
> exactly the same (as you'd expect) and then the last one jumps up by 40K.
> Is there something normally in a different section that goes into normal
> .data only in that congiguration? Might be worth looking at with:
> objdump -h vmlinux | egrep -v 'CONTENTS|ALLOC'
Given that I don't really understand what I'm looking at in this output,
all this really shows me is that, yes, .data is ~40K larger. I'd think
what we're really interested in is the contents of .data. I don't
read hex as well as I read decimal, so I converted it):
Section 344.OPT 442.OPT Delta
-------------------------------------------
.text 2135463 1783653 -351810
__ex_table 17648 16768 -880
.rodata 239127 217865 -21262
.pci_fixup 2112 2112 0
.rio_route 0 0 0
__ksymtab 34352 34352 0
__ksymtab_gpl 5808 5808 0
__kcrctab 17176 17176 0
__kcrctab_gpl 2904 2904 0
__ksymtab_strings 54818 54818 0
__param 2360 2360 0
.data 386816 427160 40344
.bss 479984 479984 0
.data.cacheline_aligned 16896 16896 0
.data.read_mostly 3104 3104 0
.vsyscall_0 295 255 -40
.xtime_lock 4 4 0
.vxtime 48 48 0
.wall_jiffies 8 8 0
.sys_tz 8 8 0
.sysctl_vsyscall 4 4 0
.xtime 16 16 0
.jiffies 8 8 0
.vsyscall_1 41 40 -1
.vsyscall_2 8 8 0
.vsyscall_3 8 8 0
.data.init_task 8192 8192 0
.init.text 106076 87536 -18540
.init.data 44016 44016 0
.init.setup 2160 2160 0
.initcall.init 1048 1048 0
.con_initcall.init 8 8 0
.security_initcall.init 0 0 0
.altinstructions 331 307 -24
.altinstr_replacement 46 43 -3
.exit.text 1548 1147 -401
.init.ramfs 134 134 0
.comment 11592 11592 0
.note.GNU-stack 0 0 0
Kurt
--
It is easier to write an incorrect program than understand a correct
one.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
