From: Derek Fawcus <dfawcus@cisco.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] impressive
Date: Wed, 26 Apr 2006 03:12:21 +0100 [thread overview]
Message-ID: <20060426031221.D22520@mrwint.cisco.com> (raw)
In-Reply-To: <20060426011933.GA20406@submarine>; from rvs@sun.com on Tue, Apr 25, 2006 at 06:19:33PM -0700
On Tue, Apr 25, 2006 at 06:19:33PM -0700, Roman Shaposhnick wrote:
> On Wed, Apr 26, 2006 at 02:11:32AM +0100, Derek Fawcus wrote:
> > Anyway, I found the culprit - libgcc has modules compiled with exception
> > handling sections; __udivdi3 and __umoddi3 get pulled from there.
>
> Well, how exactly does it relate to the original topic where we
> were discussing glibc ? libgcc is not part of glibc.
It relates to the sub thread where I linked the program with dietlibc
rather than with glibc, got a more sensible sized program, and was
then trying to figure out where the .eh_frame section came from.
The compiler I'm using does not generate .eh_frame sections by default,
so neither the testit.o file (compiled from the posted C source) nor
the input .o files from dietlibc contain such sections.
Hence my assertion that it was something the linker was doing, I had
forgotten about the existance of libgcc. Now that I know where it is
coming from, I can ignore it.
While the info you supplied was interesting, it did not directly relate
to what I was trying to figure out.
> > Mind there is a separate libgcc.a and libgcc_eh.a; I'm not sure what
> > the difference is supposed to be (the latter is about half the size).
>
> libgcc.a - Support routines, not including EH
> libgcc_eh.a - EH support routines
> libgcc_s.so - Support routines, including EH
Well maybe Suse messed up, or the compiler is simply old enought to be
doing stuff differently.
This machine does not have the .so, the _eh.a contains a bunch of unwind
routines, and the objects within libgcc.a have been compiled to include
.eh_frame sections. (GCC 3.3.3)
However the mips64 crosscompiler version of gcc 3.4.4 that I compiled up,
only has libgcc.a, and it also has .eh_frame sections in the same objects.
Looking at the C source for them, there would not appear to be any good
reason for these to have EH info - they don't call anything else.
So it just looks like GCC is always compiling the div/mod helper routines
with .eh_frame sections requested.
DF
next prev parent reply other threads:[~2006-04-26 2:12 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 20:37 Ronald G Minnich
2006-04-24 20:51 ` Charles Forsyth
2006-04-24 21:32 ` Brantley Coile
2006-04-25 11:06 ` Anthony Sorace
2006-04-25 11:08 ` Anthony Sorace
2006-04-25 2:15 ` Derek Fawcus
2006-04-25 2:23 ` Roman Shaposhnick
2006-04-25 2:37 ` Derek Fawcus
2006-04-25 3:51 ` Roman Shaposhnick
2006-04-25 8:17 ` Derek Fawcus
2006-04-25 17:53 ` Roman Shaposhnick
2006-04-26 1:11 ` Derek Fawcus
2006-04-26 1:19 ` Roman Shaposhnick
2006-04-26 2:12 ` Derek Fawcus [this message]
2006-04-25 3:02 ` Andy Newman
2006-04-25 3:13 ` Ronald G Minnich
2006-04-25 19:57 ` Dan Cross
2006-04-25 2:30 erik quanstrom
2006-04-25 2:48 ` Derek Fawcus
2006-04-25 10:20 erik quanstrom
2006-04-26 0:26 erik quanstrom
2006-04-26 0:48 ` geoff
2006-04-26 0:54 ` Roman Shaposhnick
2006-04-26 0:53 ` Roman Shaposhnick
2006-04-26 2:15 ` Taj Khattra
2006-04-26 4:59 ` David Leimbach
2006-04-26 12:37 ` Anthony Sorace
2006-04-26 15:28 ` Rian Hunter
2006-04-26 16:39 ` Micah Stetson
2006-04-26 18:02 ` Bruce Ellis
2006-04-26 20:14 ` Micah Stetson
2006-05-08 14:50 ` Harri Haataja
2006-05-08 15:04 ` LiteStar numnums
2006-05-08 15:12 ` Charles Forsyth
2006-05-08 20:08 ` Micah Stetson
2006-05-08 20:52 ` LiteStar numnums
2006-05-08 21:10 ` Jack Johnson
2006-05-08 21:17 ` andrey mirtchovski
2006-05-08 21:18 ` Paul Lalonde
2006-05-08 22:25 ` Francisco J Ballesteros
2006-05-09 21:56 ` Dave Eckhardt
2006-05-10 0:13 ` geoff
2006-05-10 8:39 ` Lluís Batlle
2006-05-08 23:31 ` geoff
2006-05-09 1:18 ` Paul Lalonde
2006-05-09 1:39 ` quanstro
2006-05-09 2:12 ` Paul Lalonde
2006-05-09 2:20 ` quanstro
2006-05-09 3:00 ` Paul Lalonde
2006-05-09 9:32 ` Bruce Ellis
2006-04-26 22:57 ` Roman Shaposhnick
2006-04-26 4:57 ` David Leimbach
2006-04-26 4:53 ` Ronald G Minnich
2006-04-26 5:11 ` Roman Shaposhnick
2006-04-26 0:55 erik quanstrom
2006-04-26 1:07 ` Roman Shaposhnick
2006-04-26 2:38 erik quanstrom
2006-04-26 3:24 jmk
2006-04-27 1:10 erik quanstrom
2006-04-27 2:06 ` Jack Johnson
2006-04-27 1:23 erik quanstrom
2006-04-27 5:08 ` Micah Stetson
2006-04-27 1:35 erik quanstrom
2006-04-27 2:13 erik quanstrom
2006-05-08 22:02 erik quanstrom
2006-05-10 0:45 erik quanstrom
2006-05-10 2:09 ` Lyndon Nerenberg
2006-05-10 3:35 ` David Arnold
2006-05-10 4:03 ` Lyndon Nerenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060426031221.D22520@mrwint.cisco.com \
--to=dfawcus@cisco.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).