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:46:24 -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> <20020315152842.A26146@redhat.com> <orelilqu9g.fsf@free.redhat.lsd.ic.unicamp.br>
On Fri, Mar 15, 2002 at 08:35:39PM -0300, Alexandre Oliva wrote:
> More specifically, and static libc that uses __divdi3, since a shared
> one would have its own __divdi3, no?
In theory. But I wouldn't expect static libc to have a different
set of symbols than shared libc. *shrug*
> However, I kind of fail to see the point of having -lgcc before -lc.
There are symbols in libgcc that require symbols from libc.
Ideally we'd be using some permutation of
--start-group -lgcc_eh -lgcc -lc --end-group
but that's a gnu ld thing.
r~