From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: ghazi@caipclassic.rutgers.edu (Kaveh R. Ghazi)
Cc: zackw@panix.com, dave.anglin@nrc.ca, gcc@gcc.gnu.org, nix@esperi.org.uk
Subject: Re: What systems (if any) have fprintf_unlocked?
Date: Mon, 15 Aug 2005 19:04:00 -0000 [thread overview]
Message-ID: <200508151904.j7FJ4Kar018844@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <200508151822.j7FIMVs1013085@caipclassic.rutgers.edu> from "Kaveh R. Ghazi" at Aug 15, 2005 02:22:31 pm
> > 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
>
> Hmm, I found another interesting reference to fprintf_unlocked here:
> http://gcc.gnu.org/ml/gcc-patches/2003-03/msg00805.html
>
> In it Dave points out that hpux is missing fputc_unlocked and
> therefore neither fputs_unlocked or fprintf_unlocked should transform
> into fputc_unlocked.
>
> Dave, does hpux have fprintf_unlocked or was mentioning it a mistake?
It doesn't have either fprintf_unlocked or fputc_unlocked.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
prev parent reply other threads:[~2005-08-15 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 15:29 Kaveh R. Ghazi
2005-08-14 17:30 ` Zack Weinberg
2005-08-15 15:17 ` Nix
2005-08-15 17:59 ` Zack Weinberg
2005-08-15 18:22 ` Kaveh R. Ghazi
2005-08-15 19:04 ` John David Anglin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508151904.j7FJ4Kar018844@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=dave.anglin@nrc.ca \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caipclassic.rutgers.edu \
--cc=nix@esperi.org.uk \
--cc=zackw@panix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).