From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20968 invoked by alias); 26 Mar 2008 18:09:59 -0000 Received: (qmail 20958 invoked by uid 22791); 26 Mar 2008 18:09:58 -0000 X-Spam-Check-By: sourceware.org Received: from mgcp1.bloomberg.com (HELO mgcp1.bloomberg.com) (208.22.56.39) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 26 Mar 2008 18:09:36 +0000 Received: from ny1520.bloomberg.com ([10.16.11.97]) by mgcp1.bloomberg.com with ESMTP; 26 Mar 2008 14:09:34 -0400 Received: from NY2528-DR.corp.bloomberg.com (ny2528-dr.corp.bloomberg.com [10.14.21.30]) by ny1520.bloomberg.com (8.14.1/8.14.1) with ESMTP id m2QI9Vl2027477; Wed, 26 Mar 2008 14:09:31 -0400 Received: from ny2545.corp.bloomberg.com ([172.20.73.98]) by NY2528-DR.corp.bloomberg.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Mar 2008 14:09:31 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Mar 2008 18:18:00 -0000 Message-ID: In-Reply-To: <20080326180616.GA5705@lunn.ch> References: <20080326180616.GA5705@lunn.ch> From: "Chris Zimman" To: "Andrew Lunn" Cc: X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] ARM EABI port / static constructor priority removal X-SW-Source: 2008-03/txt/msg00153.txt.bz2 > Given that this is used in a number of places scattered all over the > code, how do you propose to do this? What is you concept to ensure the > constructors are called in the right order? Ordering is preserved within one translation unit by C++ spec, just not between multiple translation units. BTW, I think the ARM EABI stuff will get fixed (CodeSourcery is looking at = it right now), I just think this is bad behavior to rely on in general. It's not part of EABI and was somewhat reluctantly added to EABI GCC. --Chris -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss