From: Sergei Organov <osv@Javad.RU>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] vfnprintf and floating point.
Date: Wed, 29 Sep 1999 05:30:00 -0000 [thread overview]
Message-ID: <87g0zxyk2p.fsf@osv.javad.ru> (raw)
Hello,
I just tried to separate floating point code from 'vfnprintf'
routine. It was surprisingly easy to do, but I remember that it didn't
seem so easy for similar code found in 'newlib'. The code found in
eCos libc is much better organized, but it seems that "Inf" and "NaN"
processing was removed from the code entirely. What's the reason?
If you interested, I just changed first argument of 'cvt' from
'double' to 'va_list*', and moved double argument extraction to this
routine. I also provided 'void skip_double(va_list*)' that is used to
skip double argument when floating point support is disabled in
'vfnprintf'.
Sergei.
next reply other threads:[~1999-09-29 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 5:30 Sergei Organov [this message]
1999-10-05 7:51 ` Jonathan Larmour
1999-10-06 4:34 ` Sergei Organov
1999-10-06 4:44 ` [ECOS] " Bart Veer
1999-10-06 6:04 ` Sergei Organov
1999-10-06 7:27 ` Bart Veer
1999-10-06 7:49 ` Sergei Organov
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=87g0zxyk2p.fsf@osv.javad.ru \
--to=osv@javad.ru \
--cc=ecos-discuss@sourceware.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).