From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: problems with to_string not declared in this scope
Date: Mon, 26 Oct 2015 11:15:00 -0000 [thread overview]
Message-ID: <20151026103602.GD31990@calimero.vinschen.de> (raw)
In-Reply-To: <CAOC2fq9h_ftPcGBS46CMavz8FBw=4vMftUB-oXn8AeSjiM_OcQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
On Oct 25 11:25, Michael Enright wrote:
> On Sat, Oct 24, 2015 at 10:31 PM, JonY wrote:
> >
> > On 10/25/2015 01:00, Michael Enright wrote:
> > >
> > > I sometimes wonder what would be involved in fixing this.
> > >
> >
> > Full C99 *printf support. Corinna answered on the same thread
> > https://sourceware.org/ml/cygwin/2015-01/msg00245.html
> >
>
> Yes, but what I was wondering about was the first couple of levels of
> detail below that, i.e. which algorithms, having yet to be coded in
> newlib, are needed to enable long double textification in newlib? I
> know practical methods for textifying integers but as far as I know
> floats are harder. Maybe I could use the parable of the stone soup and
> get the work rolling by offering a filename? ldtostr.c
Textifying the numbers is not the problem, there's already the ldtoa
functionality. Missing the set of long double functions is. I think
it's not the GLIBCXX_HAVE_BROKEN_VSWPRINTF, but the _GLIBCXX_USE_C99
flag or something like that. JonY?
It would still be nice if somebody with a bit of math knowledge would
contribute the missing long double functions to newlib.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-26 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 15:37 Luong Hoang
2015-10-25 5:32 ` Michael Enright
2015-10-25 10:32 ` JonY
2015-10-25 13:03 ` Csaba Raduly
2015-10-25 21:11 ` Michael Enright
2015-10-26 11:15 ` Corinna Vinschen [this message]
2015-10-26 16:28 ` Achim Gratz
2015-10-27 10:49 ` Corinna Vinschen
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=20151026103602.GD31990@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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).