From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 963FC3850404; Tue, 16 Mar 2021 14:05:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 963FC3850404
From: "michalz at nvidia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99613] Static variable destruction order race condition
Date: Tue, 16 Mar 2021 14:05:39 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: michalz at nvidia dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-99613-4-36ROZSlLuE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-99613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-99613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2021 14:05:39 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D99613

--- Comment #14 from Michal Zientkiewicz <michalz at nvidia dot com> ---
https://eel.is/c++draft/basic.start.term#3

If the completion of the constructor or dynamic initialization of an object
with static storage duration strongly happens before that of another, the
completion of the destructor of the second is sequenced before the initiati=
on
of the destructor of the first.
If the completion of the constructor or dynamic initialization of an object
with thread storage duration is sequenced before that of another, the
completion of the destructor of the second is sequenced before the initiati=
on
of the destructor of the first.
If an object is initialized statically, the object is destroyed in the same
order as if the object was dynamically initialized.
For an object of array or class type, all subobjects of that object are
destroyed before any block variable with static storage duration initialized
during the construction of the subobjects is destroyed.
If the destruction of an object with static or thread storage duration exits
via an exception, the function std=E2=80=8B::=E2=80=8Bterminate is called (=
[except.terminate]).

I think that makes at least the dependent variable case a requirement.=