Re: egcs on AIX: native or gnu ld?

[mrs@wrs.com (Mike Stump)]

> To: Andrey Slepuhin <pooh@msu.ru>
> Cc: egcs@cygnus.com
> Date: Mon, 20 Oct 97 13:36:49 -0400
> From: David Edelsohn <dje@watson.ibm.com>

> Andrey> Well, GLOBAL__DI/DD symbols are automatically exported by
> Andrey> collect2. But what about __eh_<something> symbols, which are
> Andrey> defined for each object file and are global bss symbols?
> Andrey> Should I export them or they can be omitted?

> I guess that I do not understand exception handling and how __eh_*
> symbols are handled well enough to know if they need to be exported.
> Someone who understand the C++ implementation needs to examine this.
> A symbol needs to be exported if it will be referenced by name
> outside its module.
>
> 	If C++ applications have the names of __eh_* symbols in other
> modules compiled in, then it would seem that exports are necessary.  In
> that case, one needs to expand collect2.c:scan_prog_file() to add __eh_*
> symbols to the export list along with constructors and destructors.

Given the above, I say Add them (by exact name, no .* regexs please),
they need to be exported.