From: Richard Henderson <rth@cygnus.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: law@cygnus.com, egcs@cygnus.com
Subject: Re: egcs-980315, gen*.c system.h and fatal() using stdarg/varargs
Date: Fri, 27 Mar 1998 15:18:00 -0000 [thread overview]
Message-ID: <19980326093858.00192@dot.cygnus.com> (raw)
In-Reply-To: <199803241750.MAA00882@caip.rutgers.edu>
On Tue, Mar 24, 1998 at 12:50:32PM -0500, Kaveh R. Ghazi wrote:
> #if !defined(HAVE_VPRINTF) && !defined(vfprintf)
> # ifdef HAVE_DOPRNT
> # define vfprintf(stream, format, args) _doprnt(format, args, stream)
> # else
> # define vfprintf(stream, format, args) \
> do { \
> HOST_WIDE_INT a0 = va_arg(args, HOST_WIDE_INT); \
> HOST_WIDE_INT a1 = va_arg(args, HOST_WIDE_INT); \
Ug. I would much prefer to define a proper vfprintf function than
to much with this kind of nonsense. If this is done by just doing
the argument parsing bits of vfprintf and fobing the actual formatting
off to fprintf, this should not be that large or complicated.
r~
next prev parent reply other threads:[~1998-03-27 15:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-24 11:16 Kaveh R. Ghazi
1998-03-24 11:16 ` Jeffrey A Law
1998-03-25 7:49 ` Robert Lipe
1998-03-25 16:30 ` Jeffrey A Law
1998-03-27 15:18 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-03-30 16:18 Kaveh R. Ghazi
1998-03-27 15:18 Kaveh R. Ghazi
1998-03-27 4:21 ` Richard Henderson
1998-03-26 21:54 Kaveh R. Ghazi
1998-03-27 4:21 ` Jeffrey A Law
1998-03-28 19:24 ` H.J. Lu
1998-03-26 21:54 Kaveh R. Ghazi
1998-03-29 5:14 ` John Carr
1998-03-25 17:05 Kaveh R. Ghazi
1998-03-27 15:18 ` Jeffrey A Law
1998-03-27 15:18 ` H.J. Lu
1998-03-24 14:49 Kaveh R. Ghazi
1998-03-24 10:24 Kaveh R. Ghazi
1998-03-20 8:45 Kaveh R. Ghazi
1998-03-20 8:45 ` Jeffrey A Law
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=19980326093858.00192@dot.cygnus.com \
--to=rth@cygnus.com \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--cc=law@cygnus.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).