From: Peter Bergner <bergner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble [PR104208, PR87496]
Date: Fri, 18 Mar 2022 14:19:02 -0500 [thread overview]
Message-ID: <d467c3de-ddbd-f644-452c-a9b6c1507d96@linux.ibm.com> (raw)
In-Reply-To: <20220316123314.GJ614@gate.crashing.org>
On 3/16/22 7:33 AM, Segher Boessenkool wrote:
> On Tue, Mar 15, 2022 at 02:49:39PM -0500, Peter Bergner wrote:
>> The trunk patch has been confirmed to fix the glibc build errors and no issues
>> with the patch has surfaced, so ok for the GCC11 and GCC10 release branches?
>
> If you can confirm it fixes the glibc build error on 11 and 10 as well,
> then yes please. Thanks!
I confirmed I see the same glibc issue with unpatched gcc11 and gcc10 compilers
and that the patched gcc11 and gcc10 fix the issue so I went ahead and pushed
the backports. Thanks!
Peter
prev parent reply other threads:[~2022-03-18 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b96a6329-2665-9326-3c21-e507aaf3ba70@linux.ibm.com>
[not found] ` <CAGWvny=F0AXGYHQW7vvFx_54vfcdi3Ud+EOtffejLYj9PtPXuQ@mail.gmail.com>
[not found] ` <e0cc8161-b60b-3c98-8214-4cfc673598fb@linux.ibm.com>
[not found] ` <c545d2dd-b6b2-0669-f42d-66d0d4a296e9@linux.ibm.com>
[not found] ` <cd0a5694-fd6a-ffe5-2364-14cc1e569a3f@linux.ibm.com>
2022-03-15 19:49 ` Peter Bergner
2022-03-16 12:33 ` [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm, ieee}longdouble " Segher Boessenkool
2022-03-18 19:19 ` Peter Bergner [this message]
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=d467c3de-ddbd-f644-452c-a9b6c1507d96@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).