This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc4 and local statics

From: Christopher Faylor <me at cgf dot cx>
To: cygwin-developers at cygwin dot com
Date: Wed, 18 May 2005 19:06:32 -0400
Subject: Re: gcc4 and local statics
References: <428A7520.7FD9925C@dessent.net> <20050518080133.GA25438@calimero.vinschen.de> <428B8ECB.957836A6@dessent.net> <20050518200505.GE4502@trixie.casa.cgf.cx> <428BA4E7.16145F6B@dessent.net> <20050518204556.GF4502@trixie.casa.cgf.cx> <428BB62C.E417AF1E@dessent.net>
Reply-to: cygwin-developers at cygwin dot com

On Wed, May 18, 2005 at 02:39:56PM -0700, Brian Dessent wrote:
>I'm still seeing the cygheap_user::init problem, but it's looking very
>probable that it's just another case of a static object that was
>supposed to be initialized but is actually 0.

AFAICT, the vast majority of the cases of static initialization in
cygwin seem to assume link-time initialization rather than runtime
initialization so moving things to file scope is actually the right
solution.

I've just done more than half of them and actually fixed one function
which wasn't thread safe.

cgf

References:
- gcc4 and local statics
  - From: Brian Dessent
- Re: gcc4 and local statics
  - From: Christopher Faylor
- Re: gcc4 and local statics
  - From: Brian Dessent
- Re: gcc4 and local statics
  - From: Christopher Faylor
- Re: gcc4 and local statics
  - From: Brian Dessent

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]