From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: 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: Re: [power-ieee128] What should the math functions be annotated with?
Date: Thu, 2 Dec 2021 00:05:09 +0100 [thread overview]
Message-ID: <20211201230509.GB2664@tucnak> (raw)
In-Reply-To: <20211201205447.GD2646553@tucnak>
On Wed, Dec 01, 2021 at 09:54:50PM +0100, Jakub Jelinek wrote:
> sinl in C when compiled with -mabi=ieeelongdouble), but I'm not sure
> if those need to be declared by libgfortran or math.h declares them).
To answer this myself, just tried on Fedora 34 and we'd need to
declare those ourselves.
Because math.h for -mabi=ibmlongdouble (which we want to compile
the libgfortran *.c files with so that REAL16 is long double as before)
only has prototypes like:
extern long double sinl (long double __x) __attribute__ ((__nothrow__ , __leaf__)); extern long double __sinl (long double __x) __attribute__ ((__nothrow__ , __leaf__));
and with -mabi=ieeelongdouble it has:
extern long double sinl (long double __x) __asm__ ("" "__sinieee128") __attribute__ ((__nothrow__ , __leaf__)); extern long double __sinl (long double __x) __asm__ ("" "____sinieee128") __attribute__ ((__nothrow__ , __leaf__));
but in neither case there is what we actually need for libgfortran,
which is
extern __float128 __sinieee128 (__float128) __attribute__ ((__nothrow__, __leaf__));
Jakub
next prev parent reply other threads:[~2021-12-01 23:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 20:34 Thomas Koenig
2021-12-01 20:54 ` Jakub Jelinek
2021-12-01 23:05 ` Jakub Jelinek [this message]
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=20211201230509.GB2664@tucnak \
--to=jakub@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=tkoenig@netcologne.de \
/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).