On 05/13/2014 02:52 PM, Matthew Dempsky wrote:
On Mon, May 12, 2014 at 11:26 AM, Jason Merrill <[email protected]> wrote:
"The effect of dlclosing a DSO with registered thread cleanups is
undefined."
Do you mean "undefined" as in the C++ standard nasal demons sense, or
just unspecified/implementation-defined?
Demons. Realistically, the likely possibilities are "no effect" and
"SEGV when we try to run the cleanups".
That seems reasonable, I was just trying to allow for implementations that
don't have any way to implement that, because they can't change the dynamic
loader.
That's fair, though I'd argue that's the burden of the implementation
to push for appropriate mechanisms in their dependencies to implement
the needed functionality. Are there platforms + toolchain
combinations where this is unreasonable?
Well, GCC supports lots of platforms that don't also use glibc.
Jason
_______________________________________________
cxx-abi-dev mailing list
[email protected]
http://sourcerytools.com/cgi-bin/mailman/listinfo/cxx-abi-dev
