public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tim Prince <n8tm@aol.com>
To: cygwin@cygwin.com
Subject: Re: newlib and long-double question
Date: Sun, 10 Apr 2011 18:48:00 -0000	[thread overview]
Message-ID: <4DA1B193.9080207@aol.com> (raw)
In-Reply-To: <E1896519D4C841C289335ECC3AD7E470@desktop2>

On 4/10/2011 4:28 AM, Sisyphus wrote:
>
> ----- Original Message ----- From: "Hugh Myers"
>
>> The OP is trying to build Perl itself, not use it; hence the need for
>> long double support functions...
>
> You don't need "long double support functions" to build perl ... unless
> you want to build a perl whose NV is a long double (instead of a double).
>
> Presumably the op wants to build a perl whose NV is a long double so
> that he can make use of that extra precision. Given that he can't build
> such a perl, the next best way of accessing that extra precision he
> wants is, imo, to use Math::MPFR.
>
I never did see a clear description of OP's goals.  "Performance" was 
among them, so it was unclear why typical mathlinline.h content would 
have been rejected e.g.

__inline_mathcode_ (long double, __sqrtl, __x, return __builtin_sqrtl (__x))


As OP indicated, the functions might not have been difficult to write, 
perhaps not as difficult as settling requirements. If the requirement 
was for sqrtl to perform faster than sqrt, the expectation was misguided.


-- 
Tim Prince

--
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-10 13:33 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 [this message]
2011-04-11 17:45                 ` N. C.
2011-04-12  2:31             ` N. C.
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=4DA1B193.9080207@aol.com \
    --to=n8tm@aol.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).