From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
Michael Meissner <meissner@linux.ibm.com>,
Jonathan Wakely <jwakely@redhat.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000, v3: Fix up __SIZEOF_{FLOAT, IBM}128__ defines [PR99708]
Date: Thu, 10 Mar 2022 15:36:58 -0500 [thread overview]
Message-ID: <Yiphauk1ZX70RthT@toto.the-meissners.org> (raw)
In-Reply-To: <20220309225701.GU614@gate.crashing.org>
On Wed, Mar 09, 2022 at 04:57:01PM -0600, Segher Boessenkool wrote:
> On Wed, Mar 09, 2022 at 10:10:07PM +0100, Jakub Jelinek wrote:
> > On Wed, Mar 09, 2022 at 02:57:20PM -0600, Segher Boessenkool wrote:
> > > But __ibm128 should *always* be supported, so this is a hypothetical
> > > problem.
> >
> > I bet that will require much more work. I think for the barely supported
> > (or really unsupported?) case of old sysv IEEE quad
>
> The "q" library routines are double-double. On RIOS2 (POWER2) there
> were "quad" instructions that worked on a pair of FP regs, but that was
> handled as a pair of FP regs, and since 2012 we do not support POWER2
> anymore anyway.
>
> I have no clue if and when the "q_" library routines are used. The do
> take KFmode params (or TFmode if we use double-double preferably).
>
> Or are you thinking of something else still?
Probably libquadmath (which we still build). Libquadmath defines all of the
functions with a 'q' suffix.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
next prev parent reply other threads:[~2022-03-10 20:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 8:21 [PATCH] rs6000: Fix up __SIZEOF_{FLOAT,IBM}128__ " Jakub Jelinek
2022-03-07 21:37 ` [PATCH] rs6000: Fix up __SIZEOF_{FLOAT, IBM}128__ " Segher Boessenkool
2022-03-09 13:27 ` [PATCH] rs6000, v2: " Jakub Jelinek
2022-03-09 14:00 ` Jonathan Wakely
2022-03-09 18:34 ` Segher Boessenkool
2022-03-09 19:24 ` Jakub Jelinek
2022-03-09 20:57 ` Segher Boessenkool
2022-03-09 21:10 ` [PATCH] rs6000, v3: " Jakub Jelinek
2022-03-09 22:57 ` Segher Boessenkool
2022-03-10 9:35 ` Jakub Jelinek
2022-03-10 10:37 ` Segher Boessenkool
2022-03-10 20:36 ` Michael Meissner [this message]
2022-03-10 20:44 ` [PATCH] rs6000: Fix up __SIZEOF_{FLOAT,IBM}128__ " 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=Yiphauk1ZX70RthT@toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jwakely@redhat.com \
--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).