------- Comment #5 from dannysmith at users dot sourceforge dot net 2009-01-16
07:14 -------
(In reply to comment #4)
> I've just run into this problem too.
> In earlier versions of Aaron's shared libgcc patch, we extracted ctors.o and
> chkstk.o and placed them whole into the import lib. I'm not sure why he
> didn't
> do this in the committed version, but it has the effect that you have to link
> against the static libgcc as well as the shared one in order to let it fill
> out
> any missing references. I'm not sure I'm entirely comfortable with that,
> although I can't think of any obvious problem, but it seems wrong to link
> against such a duplicated body of code to me, and I think I'd prefer the
> import
> lib solution for cygwin's compiler.
If you look at the (static) libgcc.a, when shared libs are enabled, it
contains only symbols that are not exported from the shared dll. Only the
'API-stable' symbols are exported. That is a good thing. So the libgcc.a code
does not duplicate any code in libgcc_s.[a|dll].
--
dannysmith at users dot sourceforge dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-01-16 07:14:38
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37660
