This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: libunwind issue with gcc 3.4 and glibc
- From: David Mosberger <davidm at napali dot hpl dot hp dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: GNU C Library <libc-alpha at sources dot redhat dot com>, davidm at hpl dot hp dot com
- Date: Mon, 12 Apr 2004 11:10:25 -0700
- Subject: Re: libunwind issue with gcc 3.4 and glibc
- References: <20040412165511.GA23755@lucon.org>
- Reply-to: davidm at hpl dot hp dot com
>>>>> On Mon, 12 Apr 2004 09:55:11 -0700, "H. J. Lu" <hjl@lucon.org> said:
HJ> There is a libunwind issue with gcc 3.4 and glibc. Basically,
HJ> libunwind causes gcc to generate incompatible libgcc_s.so.1:
HJ> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14925
HJ> There are 2 problems:
HJ> 1. Functions in libunwind aren't versioned.
And according to the C++ ABI, they shouldn't be. What's the rationale
for GCC to use versioning on those symbols? Won't that create
compatibility problems with other compilers anyhow?
--david