From: Michael Meissner <meissner@linux.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.org>,
"Kewen.Lin" <linkw@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Peter Bergner <bergner@linux.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>,
William Seurer <seurer@gcc.gnu.org>,
Raymond Harney <harney@us.ibm.com>
Subject: Ping #3: [PATCH 2/3] Make __float128 use the _Float128 type, PR target/107299
Date: Fri, 2 Dec 2022 13:01:20 -0500 [thread overview]
Message-ID: <Y4o9cIfwxBo7YLp6@toto.the-meissners.org> (raw)
In-Reply-To: <Y2HZFlHH8HuvhGL4@toto.the-meissners.org>
Ping for patches submitted on November 1st. These 3 patches are needed to be
able to build GCC for PowerPC target systems where long double is configured to
be IEEE 128-bit, such as Fedora 36.
This is for the 2nd of 3 patches.
| Date: Tue, 1 Nov 2022 22:42:30 -0400
| Subject: [PATCH 2/3] Make __float128 use the _Float128 type, PR target/107299
| Message-ID: <Y2HZFlHH8HuvhGL4@toto.the-meissners.org>
| https://gcc.gnu.org/pipermail/gcc-patches/2022-November/604836.html
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
next prev parent reply other threads:[~2022-12-02 18:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 2:39 Patch [0/3] for PR target/107299 (GCC does not build on PowerPC when long double is IEEE 128-bit) Michael Meissner
2022-11-02 2:40 ` [PATCH 1/3] Rework 128-bit complex multiply and divide, PR target/107299 Michael Meissner
2022-11-07 15:41 ` Ping: " Michael Meissner
2022-11-29 17:43 ` Ping #2: " Michael Meissner
2022-12-02 17:58 ` Ping #3: " Michael Meissner
2022-12-06 9:36 ` Kewen.Lin
2022-12-07 6:44 ` Michael Meissner
2022-12-07 7:55 ` Kewen.Lin
2022-12-08 22:04 ` Michael Meissner
2022-12-12 10:20 ` Kewen.Lin
2022-12-13 6:14 ` Michael Meissner
2022-12-13 13:51 ` Segher Boessenkool
2022-12-14 8:45 ` Kewen.Lin
2022-12-13 6:23 ` Michael Meissner
2022-11-02 2:42 ` [PATCH 2/3] Make __float128 use the _Float128 type, " Michael Meissner
2022-11-07 15:43 ` Ping: " Michael Meissner
2022-11-29 17:44 ` Michael Meissner
2022-12-02 18:01 ` Michael Meissner [this message]
2022-12-06 11:27 ` Kewen.Lin
2022-12-14 8:46 ` Kewen.Lin
2022-12-14 9:36 ` Jakub Jelinek
2022-12-14 10:11 ` Kewen.Lin
2022-12-14 10:33 ` Jakub Jelinek
2022-12-15 7:54 ` Kewen.Lin
2022-12-15 7:45 ` Kewen.Lin
2022-12-15 18:28 ` Joseph Myers
2022-12-15 18:49 ` Segher Boessenkool
2022-12-15 18:56 ` Jakub Jelinek
2022-12-15 20:26 ` Segher Boessenkool
2022-12-15 17:59 ` Segher Boessenkool
2022-12-16 0:09 ` Michael Meissner
2022-12-16 17:55 ` Segher Boessenkool
2022-12-16 21:53 ` Michael Meissner
2023-01-11 20:24 ` Michael Meissner
2022-11-02 2:44 ` [PATCH 3/3] Update float 128-bit conversions, " Michael Meissner
2022-11-07 15:44 ` Ping: " Michael Meissner
2022-11-29 17:46 ` Ping #3: " Michael Meissner
2022-12-02 18:04 ` Michael Meissner
2022-12-06 14:56 ` Patch [0/3] for PR target/107299 (GCC does not build on PowerPC when long double is IEEE 128-bit) Segher Boessenkool
2022-12-06 15:03 ` Jakub Jelinek
2022-12-13 14:11 ` Segher Boessenkool
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=Y4o9cIfwxBo7YLp6@toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=harney@us.ibm.com \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=seurer@gcc.gnu.org \
--cc=will_schmidt@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).