From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 25 Apr 2006 18:19:33 -0700
From: Roman Shaposhnick <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] impressive
Message-ID: <20060426011933.GA20406@submarine>
References: <444D3701.50303@lanl.gov> <20060425031523.N21356@mrwint.cisco.com>
	<20060425022329.GF25096@submarine>
	<20060425033704.O21356@mrwint.cisco.com>
	<20060425035117.GB25952@submarine>
	<20060425091701.Q21356@mrwint.cisco.com>
	<20060425175302.GH25096@submarine>
	<20060426021131.C22520@mrwint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <20060426021131.C22520@mrwint.cisco.com>
User-Agent: Mutt/1.4.1i
Topicbox-Message-UUID: 462d072e-ead1-11e9-9d60-3106f5b1d025

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.

> 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

Thanks,
Roman.