From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Peter Bergner <bergner@linux.ibm.com>,
Michael Meissner <meissner@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Re: [PATCH] libstdc++: Add C++ runtime support for new 128-bit long double format
Date: Mon, 30 Nov 2020 17:29:20 -0600 [thread overview]
Message-ID: <20201130232920.GH2672@gate.crashing.org> (raw)
In-Reply-To: <20201111215001.GA231697@redhat.com>
Hi!
Thank you for all this.
On Wed, Nov 11, 2020 at 09:50:01PM +0000, Jonathan Wakely wrote:
> This adds support for the new __ieee128 long double format on
> powerpc64le targets.
> * testsuite/27_numerics/complex/abi_tag.cc: Add u9___ieee128 to
> regex matching expected symbols.
One less underscore.
> libstdc++-v3/ChangeLog:
>
> * Makefile.in:
> * config.h.in:
(etc.) Something missing here?
All the actual patch looks fine to me, but that doesn't say much :-)
Segher
next prev parent reply other threads:[~2020-11-30 23:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 21:50 Jonathan Wakely
2020-11-30 21:30 ` Michael Meissner
2020-12-01 15:10 ` Jonathan Wakely
2020-12-01 16:04 ` Jonathan Wakely
2020-12-01 19:10 ` Michael Meissner
2020-12-01 21:10 ` Jonathan Wakely
2020-12-01 21:41 ` Jonathan Wakely
2020-12-01 22:25 ` Michael Meissner
2020-12-01 22:36 ` Jonathan Wakely
2020-12-01 23:24 ` Michael Meissner
2020-12-02 15:14 ` Michael Meissner
2020-12-01 23:32 ` Michael Meissner
2020-12-03 23:07 ` Tulio Magno Quites Machado Filho
2020-12-04 0:35 ` Jonathan Wakely
2020-12-10 16:14 ` Jonathan Wakely
2020-12-10 17:14 ` Peter Bergner
2020-12-10 17:27 ` Jonathan Wakely
2020-12-15 0:57 ` Tulio Magno Quites Machado Filho
2020-11-30 23:29 ` Segher Boessenkool [this message]
2020-12-01 15:04 ` Jonathan Wakely
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=20201130232920.GH2672@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--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).