This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: printing exceptions?
- From: Richard Henderson <rth at redhat dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: tromey at redhat dot com, Jeff Sturm <jsturm at one-point dot com>, Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>, Java Discuss List <java at gcc dot gnu dot org>, libtool at gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 15 Mar 2002 15:28:42 -0800
- Subject: Re: printing exceptions?
- References: <Pine.LNX.4.10.10203052317220.6889-100000@mars.deadcafe.org> <orsn7dtpij.fsf@free.redhat.lsd.ic.unicamp.br> <87u1rt4948.fsf@creche.redhat.com> <orwuwps5h1.fsf@free.redhat.lsd.ic.unicamp.br> <87664947pt.fsf@creche.redhat.com> <orpu25sb8g.fsf@free.redhat.lsd.ic.unicamp.br>
On Fri, Mar 15, 2002 at 07:43:43PM -0300, Alexandre Oliva wrote:
> Another possibility that occurred to me, that would further alleviate
> the problem of duplicate shared libraries, would be to get GCC to no
> longer issue the `-lgcc_s -lc -lgcc_s' sequence, but instead, to use
> just `-lgcc_s -lc'.
Seems ok.
> We'd might still have to add duplicates for -lgcc and -lgcc_eh...
Not for gcc_eh. The point of the duplicate is to cater to a libc
that uses e.g. __divdi3. I suspect that we can use
-lgcc_eh -lgcc -lc -lgcc
in the static case.
r~