From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: dj@redhat.com
Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org, pcarlini@unitus.it
Subject: Re: Libiberty's snprintf for v3?
Date: Tue, 22 Apr 2003 05:59:00 -0000 [thread overview]
Message-ID: <200304220302.XAA23465@caip.rutgers.edu> (raw)
In-Reply-To: <200304220052.h3M0qO830610@greed.delorie.com>
[second try, this time with a Subject:]
> From: DJ Delorie <dj@redhat.com>
>
> > But, on the upside we won't need vasprintf.c, and the resulting code
> > will probably be faster than the current implementation if we cache
> > the fd.
>
> File I/O is very expensive on Microsoft platforms (DJGPP, Cygwin,
> MinGW) compared to what you're used to under Unix platforms, even to
> /dev/null (both djgpp and cygwin emulate /dev/null, I don't know about
> mingw).
Ok, but that's only a concern if these platforms are missing
[v]snprintf and therefore would rely on the libiberty copy.
E.g. I'd expect that cygwin has snprintf. Don't know about the
others.
Can you please clarify the other platforms' situations?
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next prev parent reply other threads:[~2003-04-22 3:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EA44576.90708@unitus.it>
2003-04-22 2:19 ` Kaveh R. Ghazi
2003-04-22 2:24 ` DJ Delorie
2003-04-22 5:59 ` Kaveh R. Ghazi [this message]
[not found] ` <200304220247.WAA19945@caip.rutgers.edu>
[not found] ` <200304220313.h3M3D4c32419@greed.delorie.com>
2003-04-22 23:53 ` Kaveh R. Ghazi
2003-04-23 12:49 ` Andreas Schwab
2003-04-26 23:25 ` Kaveh R. Ghazi
2003-04-22 10:53 ` Andreas Schwab
2003-04-22 23:56 ` Kaveh R. Ghazi
2003-04-22 20:43 ` Joe Buck
2003-04-23 0:01 ` Kaveh R. Ghazi
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=200304220302.XAA23465@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=pcarlini@unitus.it \
/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).