public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Paul E. Murphy" <murphyp@linux.vnet.ibm.com>
To: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
	Steve Munroe <sjmunroe@us.ibm.com>
Subject: Re: Adding __float128 (i.e TS 18661-3)
Date: Thu, 09 Jun 2016 20:15:00 -0000	[thread overview]
Message-ID: <38e28acc-e285-96df-429e-567f4e494029@linux.vnet.ibm.com> (raw)
In-Reply-To: <c6fdca14-2c5a-4b9a-8dd9-25630c6a100e@linux.vnet.ibm.com>



On 06/09/2016 03:00 PM, Paul E. Murphy wrote:
> 
> Picking up here as a reasonable place to continue the
> discussion on ABI and API for float128 (or any future
> TS 18661-3 derived type).
> 
> 
> For any new TS 18661-3 derived type, I propose the
> following new functions and ABI be exposed through
> libm via math.h:
> 
> 	From TS 18661-3:
> 
> 	acosh acos asinh asin
> 	atan2 atanh atan cabs
> 	cacosh cacos carg casinh
> 	casin catanh catan cbrt
> 	ccosh ccos ceil cexp
> 	cimag clog conj copysign
> 	cosh cos cpow cproj
> 	creal csinh csin csqrt
> 	ctanh ctan erfc erf
> 	exp2 exp expm1 fabs
> 	fdim floor fma fmax
> 	fmin fmod frexp hypot
> 	ilogb ldexp lgamma llrint
> 	llround log10 log1p log2
> 	logb log lrint lround
> 	modf nanf nearbyint nextafter
> 	pow remainder remquo rint
> 	round scalbln scalbn 
> 	sinh sin sqrt tanh
> 	tan tgamma trunc nextup
> 	nextdown.
> 
> 	From GNU:
> 
> 	exp10 clog10 j0l j1l
> 	jnl lgamma?_r sincos
> 	y0 y1 yn
>

Err, anything taking a _Complex _FloatN argument should only
be declared via complex.h.

Likewise tgmath.h needs updated to correctly select
__float128 functions.

  reply	other threads:[~2016-06-09 20:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 21:11 Paul E. Murphy
2016-05-05 23:35 ` Joseph Myers
2016-05-05 23:56   ` Joseph Myers
2016-05-09 14:06     ` Florian Weimer
2016-05-09 14:52       ` Joseph Myers
2016-05-06 17:25   ` Paul E. Murphy
2016-05-06 22:03     ` Joseph Myers
2016-05-09 14:38       ` Szabolcs Nagy
2016-05-09 15:07         ` Joseph Myers
2016-06-09 20:00       ` Paul E. Murphy
2016-06-09 20:15         ` Paul E. Murphy [this message]
2016-06-09 20:36         ` Joseph Myers
2016-06-09 20:46         ` Joseph Myers
2016-06-10 15:57         ` Adding __float128 (i.e TS 18661-3) [v2] Paul E. Murphy
2016-06-10 17:24           ` Joseph Myers
2016-06-21 13:33           ` Joseph Myers
2016-06-07 20:32   ` Adding __float128 (i.e TS 18661-3) Steven Munroe
2016-06-07 21:22     ` Joseph Myers
2016-06-07 21:56       ` Steven Munroe
2016-06-07 22:30         ` Joseph Myers
2016-06-07 23:49           ` Steven Munroe
2016-06-08 12:33             ` Joseph Myers
2016-06-08 20:20               ` Steven Munroe

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=38e28acc-e285-96df-429e-567f4e494029@linux.vnet.ibm.com \
    --to=murphyp@linux.vnet.ibm.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sjmunroe@us.ibm.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).