This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: What systems (if any) have fprintf_unlocked?

From: "Zack Weinberg" <zackw at panix dot com>
To: "Nix" <nix at esperi dot org dot uk>
Cc: "Kaveh R. Ghazi" <ghazi at caipclassic dot rutgers dot edu>,gcc at gcc dot gnu dot org
Date: Mon, 15 Aug 2005 10:59:05 -0700 (PDT)
Subject: Re: What systems (if any) have fprintf_unlocked?
References: <200508141528.j7EFSrAO006486@caipclassic.rutgers.edu> <33546.66.92.218.83.1124040619.squirrel@mail.panix.com> <87slxbs00t.fsf@amaterasu.srvr.nix>

Nix said:
> On 14 Aug 2005, Zack Weinberg yowled:
>> Kaveh R. Ghazi said:
>>> Hmm I'm curious, what systems (if any) have fprintf_unlocked?
>>
>> At the time I thought glibc had it, but I don't see it on my (2.3.5)
>> system now.
>
> It doesn't appear in the changelogs either.
>
> Is it possible you got confused with fputs_unlocked() or something?

I'm not going to be able to remember exactly.  It might be worth looking
at various proprietary Unixes to see if they've got fprintf_unlocked, but
given the date I don't think I was looking at one of them.  My best guess
is that I simply assumed glibc had it, since it seemed to have _unlocked
variants of all the other stdio functions.

zw

Follow-Ups:
- Re: What systems (if any) have fprintf_unlocked?
  - From: Kaveh R. Ghazi

References:
- What systems (if any) have fprintf_unlocked?
  - From: Kaveh R. Ghazi
- Re: What systems (if any) have fprintf_unlocked?
  - From: Zack Weinberg
- Re: What systems (if any) have fprintf_unlocked?
  - From: Nix

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