From: FX <fxcoudert@gmail.com>
To: Jerry DeLisle <jvdelisle@verizon.net>
Cc: Fortran List <fortran@gcc.gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: Quad-float math library: licence question
Date: Fri, 13 Aug 2010 15:48:00 -0000 [thread overview]
Message-ID: <17D6A1EF-5E47-429C-A1BF-9F224EB63B68@gmail.com> (raw)
In-Reply-To: <4C655FF1.8000408@verizon.net>
> Second, can we define a F95 module interface so that one can simply do USE QUADsomename and have that automatically link in the separate library.
There is no question about how this is handled on the Fortran end: the user says "real(kind=16)".
> Third, can we not expand our current dtoa code to handle quad. Our current code is fairly flexible I think. (I have not reviewed your code yet)
Unless I'm wrong, the current code uses the system's printf functions for floating-point output, does it not? If so, because C99 (nor glibc, nor any other libc out there) provides binary128 I/O, we need to provide our own.
Regarding how to proceed, well... let's just say my opinion is that if you ask the SC to ask the FSF to ... to tell the SC to tell the community to ... then maybe this will make it into gfortran-4.9 :)
FX
next prev parent reply other threads:[~2010-08-13 15:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 14:35 FX
2010-08-13 15:12 ` Jerry DeLisle
2010-08-13 15:30 ` Steve Kargl
2010-08-13 15:51 ` Jerry DeLisle
2010-08-13 15:48 ` FX [this message]
2010-08-13 15:57 ` Jakub Jelinek
2010-08-13 15:59 ` FX
2010-08-13 16:07 ` Steve Kargl
2010-08-13 16:10 ` FX
2010-08-13 16:39 ` Jerry DeLisle
2010-08-14 11:55 ` Toon Moene
2010-08-14 12:30 ` Jakub Jelinek
2010-08-14 13:39 ` Toon Moene
2010-08-14 13:47 ` Richard Guenther
2010-08-14 15:41 ` Steve Kargl
2010-08-14 15:44 ` Jerry DeLisle
2010-08-14 17:02 ` Toon Moene
2010-08-14 17:21 ` Gerald Pfeifer
2010-08-14 19:11 ` Steve Kargl
2010-08-16 17:42 ` Toon Moene
2010-08-21 20:49 ` FX
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=17D6A1EF-5E47-429C-A1BF-9F224EB63B68@gmail.com \
--to=fxcoudert@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@verizon.net \
/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).