public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: gcc mailing list <gcc@gcc.gnu.org>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	David Edelsohn <dje.gcc@gmail.com>
Subject: [power-ieee128] What should the math functions be annotated with?
Date: Wed, 1 Dec 2021 21:34:47 +0100	[thread overview]
Message-ID: <119d695e-c316-ba5f-a3ed-963f18a67e35@netcologne.de> (raw)

I am currently working on implementing the IEEE 128-bit floating
on POWER.  One of the things to decide is what to call the
math functions for the library calls.

Example: libgfortran/generated/bessel_r16.c currently has

#if defined(GFC_REAL_16_IS_FLOAT128)
#define MATHFUNC(funcname) funcname ## q
#else
#define MATHFUNC(funcname) funcname ## l
#endif

(This is actually generated from an m4 file).

For the BesselJ functions, for example, either the library functions jnq
or jnl will be called.

We have chosen *_r17.c and _c17.c as the naming conventions for
library functions using IEEE 128-bit, and the files will be compiled
with mabi=ieeelongdouble.

So, what should the suffix for math functions be?  I assume they will be
picked up from some library.  Somebody else than me will have to make
sure this is done correctly, though :-)

Regards

	Thomas
So, what should the math functions be called so that they are actually
found in the library?


             reply	other threads:[~2021-12-01 20:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 20:34 Thomas Koenig [this message]
2021-12-01 20:54 ` Jakub Jelinek
2021-12-01 23:05   ` Jakub Jelinek
2021-12-03  7:29   ` Thomas Koenig
2021-12-03  9:28     ` Jakub Jelinek
2021-12-03 11:16       ` Thomas Koenig
2021-12-03 11:35         ` Jakub Jelinek
2021-12-03 11:56           ` Thomas Koenig
2021-12-03 14:57             ` Bill Schmidt
2021-12-04  6:39               ` Michael Meissner
2021-12-04  9:33                 ` Thomas Koenig
2021-12-04 10:16                 ` Thomas Koenig
2021-12-04 10:29                   ` Jakub Jelinek
2021-12-04 13:42                     ` Thomas Koenig
2021-12-04 15:25                       ` Michael Meissner
2021-12-04 15:37                         ` Peter Bergner
2021-12-04 16:12                           ` Peter Bergner
2021-12-04 16:19                             ` Jakub Jelinek
2021-12-04 22:27                               ` Peter Bergner
2021-12-04 17:40                             ` Thomas Koenig
2021-12-05  0:35                               ` Peter Bergner
2021-12-05 11:16                                 ` Thomas Koenig
2021-12-06 22:31                                   ` Michael Meissner

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=119d695e-c316-ba5f-a3ed-963f18a67e35@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=dje.gcc@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=segher@kernel.crashing.org \
    /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).