From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH], Update __FLOAT128_HARDWARE__ on power9
Date: Wed, 25 Oct 2017 23:57:00 -0000 [thread overview]
Message-ID: <20171025235619.GL4406@gate.crashing.org> (raw)
In-Reply-To: <20171020205640.GA8774@ibm-tiger.the-meissners.org>
On Fri, Oct 20, 2017 at 04:56:41PM -0400, Michael Meissner wrote:
> This is a simple patch to add a way that the GLIBC team call tell that certain
> __float128 built-in functions are available. While previous patches of mine
> set __FAST_FP_FMAF128, which could be used for this purpose, this macro just
> bumps __FLOAT128_HARDWARE__ to say that the built-in functions are available in
> addition to supporting the basic IEEE 128-bit floating point instructions.
I don't think this is such a great macro name for this purpose.
What problem does this solve?
Segher
next prev parent reply other threads:[~2017-10-25 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 21:06 Michael Meissner
2017-10-25 23:57 ` Segher Boessenkool [this message]
2017-10-26 0:11 ` 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=20171025235619.GL4406@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.com \
--cc=wschmidt@linux.vnet.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).