public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "N. C." <necrocowmoo@gmail.com>
To: cygwin@cygwin.com
Subject: Re: newlib and long-double question
Date: Tue, 12 Apr 2011 02:31:00 -0000	[thread overview]
Message-ID: <BANLkTi=vQM2=3G5y=V5UdsWnQ4eagLY8mg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=XbmP=4PaC6e6_Lbe37r5C9hz5-Q@mail.gmail.com>

Exactly, I really need to be able to build Perl whose NV is a long
double. And this was just one example that I gave. I honestly think it
is worth it to have long double support in cygwin (to have those
functions that are currently undefined), as it seems more and more
clear that A) there is a use for them, and B) there are cases where it
really is needed.

IIRC, the whole point of cygwin is to have a unix-like environment
within a non-unix-like system, right? Does it not make sense to make
the back bone (libc) that much mroe complete, furthur augmenting
usability and compatibility?

Again, thanks to all of you for your time and input.

- N.C.

On 4/10/11, Hugh Myers wrote:
> The OP is trying to build Perl itself, not use it; hence the need for
> long double support functions...
>
> --hsm
>
> On Sun, Apr 10, 2011 at 4:25 AM, Sisyphus <sisyphus1@optusnet.com.au> wrote:
>>
>> ----- Original Message ----- From: "marco atzeri"
>>
>>>> On a Linux system that I have access to, I see that those functions
>>>> are in /lib/libm.* but cygwin's /lib/libm.* still seems to lack them.
>>>> Is there any work around or alternate version ofthis lib that actually
>>>> has these functions. I honestly do not mean to be rude, but how
>>>> difficult is it to impliment these functions which seem so common in
>>>> most unix-like systems?
>>>
>>> It is not overcomplicated to implement it, but it takes time and
>>> someone to do it.
>>> When I implemented all the complex functions (cabs, ccos..) I spent one
>>> month
>>> to make it right. A more capable guy will take less surely, but as
>>> mention I see little
>>> benefit moving from 64 to 80 bits so I was not interested to implement
>>> it.
>>>
>>
>> I sense an opportunity here to plug (to the op) the Math::MPFR perl module
>> -
>> for which the gmp and mpfr C libraries are required.
>> I guess one could also use Math::BigFloat, but I assume the op has already
>> considered (and rejected) that option - the performance hit incurred by
>> its
>> use has always discouraged me.
>> Perhaps he has also already considered and rejected Math::MPFR, but it
>> seems
>> to me to be by far the best option for achieving added precision with
>> floating point numbers - at least until such time as building perl with
>> -Duselongdouble has been facilitated.
>>
>> Cheers,
>> Rob
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2011-04-11  2:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09 21:07 Necro Cow
2011-04-09 21:10 ` Christopher Faylor
2011-04-09 22:04   ` marco atzeri
2011-04-10 10:25     ` N. C.
2011-04-10 11:28       ` marco atzeri
2011-04-10 12:25         ` Sisyphus
2011-04-10 12:49           ` Hugh Myers
2011-04-10 13:33             ` Sisyphus
2011-04-10 15:33               ` Hugh Myers
2011-04-10 17:51                 ` Sisyphus
2011-04-10 18:48               ` Tim Prince
2011-04-11 17:45                 ` N. C.
2011-04-12  2:31             ` N. C. [this message]
2011-04-18 11:43               ` Corinna Vinschen
2011-04-10 20:05       ` Reini Urban

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='BANLkTi=vQM2=3G5y=V5UdsWnQ4eagLY8mg@mail.gmail.com' \
    --to=necrocowmoo@gmail.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).