[Bug c++/72768] Potential bug about the order of destructors of static objects and atexit() callbacks in C++?
lh_mouse at 126 dot com
gcc-bugzilla@gcc.gnu.org
Tue Aug 2 14:04:00 GMT 2016
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72768
--- Comment #8 from lh_mouse <lh_mouse at 126 dot com> ---
(In reply to Jonathan Wakely from comment #7)
> It *could* check, but that doesn't mean it should.
I was merely stating that the twice-destruction problem wasn't unresolvable.
The topic about the C++ standard starts here:
https://groups.google.com/a/isocpp.org/forum/#!topic/std-discussion/VipjQOBUg6M
More information about the Gcc-bugs
mailing list