From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18840 invoked by alias); 28 May 2009 20:16:07 -0000 Received: (qmail 18809 invoked by alias); 28 May 2009 20:15:57 -0000 Date: Thu, 28 May 2009 20:16:00 -0000 Message-ID: <20090528201557.18808.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/40094] FAIL: ext/throw_allocator/deallocate_global.cc execution test In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dave at hiauly1 dot hia dot nrc dot ca" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-05/txt/msg02218.txt.bz2 ------- Comment #18 from dave at hiauly1 dot hia dot nrc dot ca 2009-05-28 20:15 ------- Subject: Re: FAIL: ext/throw_allocator/deallocate_global.cc execution test > At least, now we are sure the issue was not caused by my tentative fixes to > throw_allocator. My conclusion was that this is a target bug involving the ordering of atexit and static destructors. The C++ standard apparently requires that these be interleaved based on the order of registration. I don't think it would be possible to achieve full compliance because of the limited capability of atexit, but it might be possible to change the ordering. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40094