Re: hiding of (global) C++ symbols in shared object

2000-05-15 Thread Richard Henderson
On Mon, May 15, 2000 at 01:00:29PM +0200, Jakub Jelinek wrote: > What about using symbol version map? > Say: > > MYPLUGIN { > global: > init_plugin; what__C9exception; ... Incidentally, version maps do support extern "C++" { some_class::function other_class::*

Re: printing exceptions?

2002-03-15 Thread Richard Henderson
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

Re: printing exceptions?

2002-03-15 Thread Richard Henderson
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

Re: printing exceptions?

2002-03-30 Thread Richard Henderson
On Sat, Mar 30, 2002 at 06:18:19AM -0300, Alexandre Oliva wrote: > * gcc.c (LIBGCC_SPEC): Folded %L and duplicate %G here... > (LINK_COMMAND_SPEC): ... from here. > (init_gcc_specs): Duplicate it here too, omitting > shared_name in the second copy. > (init_spec): Tes