This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: printing exceptions?
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, Richard Henderson <rth at redhat dot com>, 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: Sat, 16 Mar 2002 01:10:09 +0100
- 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> <jen0x95qhg.fsf@sykes.suse.de>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Sat, Mar 16, 2002 at 01:02:51AM +0100, Andreas Schwab wrote:
> Alexandre Oliva <aoliva@redhat.com> writes:
>
> |> However, I kind of fail to see the point of having -lgcc before -lc.
>
> The point of having -lgcc before -lc is that -lgcc can add references to
> -lc functions that were not referenced before. If you have -lgcc only
> after -lc those references cannot be resolved in a static link.
Though for !static !shared-libgcc, I think:
-lc -lgcc -lc_nonshared
is best, so that symbols are preferably satisfied from shared libc.
Jakub