From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: gcc mailing list <gcc@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Michael Meissner <meissner@linux.ibm.com>,
Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Re: [power-ieee128] What should the math functions be annotated with?
Date: Fri, 3 Dec 2021 10:28:25 +0100 [thread overview]
Message-ID: <20211203092825.GN2646553@tucnak> (raw)
In-Reply-To: <af385ac2-f719-ca9b-6001-311e019daaeb@netcologne.de>
On Fri, Dec 03, 2021 at 08:29:53AM +0100, Thomas Koenig wrote:
>
> On 01.12.21 21:54, Jakub Jelinek via Fortran wrote:
>
> > Inside of libgfortran, I think it should depend on some macro defined
> > in libgfortran.h.
> > #if defined(__powerpc64__) && __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__ \
> > && defined __GLIBC_PREREQ && __GLIBC_PREREQ (2, 32)
> > then
> > #define MATHFUNC(funcname) __ ## funcname ## ieee128
> > (i.e. use the functions that will be used when one uses e.g.
> > 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).
> > Otherwise (when libgfortran is compiled against glibc older than 2.32)
> > it should use
> > #define MATHFUNC(funcname) funcname ## q
> > i.e. use the libquadmath APIs).
>
> The current Ubuntu does not have these functions:
>
> ubuntu@gcc-fortran:/lib/powerpc64le-linux-gnu$ nm libm.a 2>/dev/null | grep
> ieee128
> ubuntu@gcc-fortran:/lib/powerpc64le-linux-gnu$
>
> Will they be supplied in the future, or with the advanced toolchain?
It is part of upstream glibc 2.32 (released Aug 2020) and later, see
https://sourceware.org/git/?p=glibc.git;a=commit;h=051be01f6b41a1466b07ae4bd7f5894a8ec5fe67
distrowatch says that glibc 2.32 and later is in Ubuntu 21.04 and later.
Jakub
next prev parent reply other threads:[~2021-12-03 9:28 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
2021-12-03 7:29 ` Thomas Koenig
2021-12-03 9:28 ` Jakub Jelinek [this message]
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=20211203092825.GN2646553@tucnak \
--to=jakub@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=tkoenig@netcologne.de \
--cc=wschmidt@linux.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).