This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Problem with `string', threading and shared libraries.
- To: Gabriel Dos Reis <gdr at codesourcery dot com>
- Subject: Re: Problem with `string', threading and shared libraries.
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 28 Sep 2001 18:40:28 -0300
- Cc: Carlo Wood <carlo at alinoe dot com>, gcc-bugs at gcc dot gnu dot org, gcc at gcc dot gnu dot org, stl at sgi dot com, libstdc++ at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <20010928164914.A32098@alinoe.com><or8zezvx90.fsf@localhost.localdomain><flelor6lw8.fsf@jambon.cmla.ens-cachan.fr>
On Sep 28, 2001, Gabriel Dos Reis <gdr@codesourcery.com> wrote:
> Alexandre Oliva <aoliva@redhat.com> writes:
> | On Sep 28, 2001, Carlo Wood <carlo@alinoe.com> wrote:
> |
> | > I was wondering, how can it be that `string' has a different
> | > mangling on different compilers/machines? Isn't that a bug?
> |
> | Well, it can be argued that they are actually two different classes,
> If they are really considered to be two different classes, then
> "std::string" is a truly bad choice.
Well, using different compilers can always result in different
mangling for std::string. In this case, it's the same version of GCC
built with different configure arguments, but the configure arguments
still make them different compilers.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me