This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: crosstool bloat

From: David Karlton <dkarlton at themediamall dot com>
To: Peter Barada <peter at the-baradas dot com>
Cc: dave dot korn at artimi dot com, crossgcc at sourceware dot org
Date: Sun, 18 Sep 2005 23:15:35 -0400
Subject: Re: crosstool bloat
References: <SERRANO2Why7DYiLLjk00000066@SERRANO.CAM.ARTIMI.COM> <432E1905.3060309@themediamall.com> <20050919030813.70FEE98428@baradas.org>

Peter Barada wrote:

Being as far from a guru at this stuff as humanly possible, the best I could figure out was that the bloated programs have an additional section header named ".MIPS.stubs". I'm not sure how else to use objdump effectively. Forgive my inexperience with compilers and such... Is there another arg I should try to compare?
Start with 'objdump -h' to dump the section headers.  From there you
cans ee the size of each section(and whether there are any new and/or
unexpected ones).

That's exactly what I did, and the bloated one had an additional section:

Idx Name          Size      VMA       LMA       File off  Algn
10 .MIPS.stubs   000000a0  00400e50  00400e50  00000e50  2**2

but I don't know what this really means.

dk


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

Follow-Ups:
- Re: crosstool bloat
  - From: Peter Barada

References:
- RE: crosstool bloat
  - From: Dave Korn
- Re: crosstool bloat
  - From: David Karlton
- Re: crosstool bloat
  - From: Peter Barada

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]