This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: threadsafeness at egcs1.0.3 and 1.1
- To: Ulrich Drepper <drepper at cygnus dot com>
- Subject: Re: threadsafeness at egcs1.0.3 and 1.1
- From: Nicholas Lee <nlee011 at math dot auckland dot ac dot nz>
- Date: Wed, 15 Jul 1998 11:57:19 +1200 (NZST)
- cc: egcs at cygnus dot com
- Reply-To: Nicholas Lee <nlee011 at math dot auckland dot ac dot nz>
On 13 Jul 1998, Ulrich Drepper wrote:
> n.lee@math.auckland.ac.nz (Nicholas Lee) writes:
>
> > His basic comment is that function statics have value in that they nail
> > down the point of initialisation a some function call time.
>
> I don't know whether I understand this sentence. But it seems this is
> exactly what we are talking about. We have to initialise the function
> static, but how is the question. It's no problem in single-threaded
> programs, we are talking about multi-threaded programs.
He compares it with Class and global statics where the order of
initialisation is fixed within translation units, but not across them.
Class Static initialisation order might be even more of a problem in a
threaded application, where different threads might enter different
translation units at different times or at the same time.
Nicholas
--
"I reserve the right to contradict myself."
Nicholas Lee (Li Peng Ming) n.lee with math.auckland.ac in nz
Auckland University, New Zealand