 |
|
|
|
Actions
|
|
[ Date Prev][ Date Next][ Thread Prev][ Thread Next][ Date Index][ Thread Index]
Re: [cxx-abi-dev] ABI modification for exception propagation
- To: Sebastian Redl <sebastian.redl@xxxxxxxxxxxxxx>
- Subject: Re: [cxx-abi-dev] ABI modification for exception propagation
- From: Mark Mitchell <mark@xxxxxxxxxxxxxxxx>
- Date: Tue, 27 May 2008 14:16:36 -0700
Sebastian Redl wrote:
David Vandevoorde wrote:
On May 27, 2008, at 4:39 AM, Sebastian Redl wrote:
This might work. But *only* if all modules link to the support
library dynamically, of course. If any of them links statically, it
would keep the old implementation, which would wreak havoc.
That seems a reasonable restriction to me. Linking an application or
shared library statically with the C++ run-time library -- and then
trying to combine that with some other C++ shared library or
application, also linked with the run-time library -- seems very dodgy
to me. After all, there's global data in there. The cases that concern
me are object files, or existing shared libraries linked dynamically
against the C++ run-time library.
I don't think G++ static links the C++ run-time library into a shared
library if you just do "g++ -shared -o libfoo.so x.cpp", does it?
Thanks,
--
Mark Mitchell
CodeSourcery
mark@xxxxxxxxxxxxxxxx
(650) 331-3385 x713
|
|