This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/72768] Potential bug about the order of destructors of static objects and atexit() callbacks in C++?
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 02 Aug 2016 08:54:00 +0000
- Subject: [Bug c++/72768] Potential bug about the order of destructors of static objects and atexit() callbacks in C++?
- Auto-submitted: auto-generated
- References: <bug-72768-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72768
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> It is necessary for correctness that destructors are run for objects which
> have completed a constructor. It is not necessary for correctness to order
> static destructors after the destructor for an object still being
Oops, I meant atexit callbacks, not static destructors.