public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@linux.ibm.com>
To: David Edelsohn <dje.gcc@gmail.com>,
	Segher Boessenkool <segher@kernel.crashing.org>
Cc: 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: Tue, 15 Mar 2022 14:49:39 -0500	[thread overview]
Message-ID: <8c003ae0-8bf7-62f1-2760-0340e05502df@linux.ibm.com> (raw)
In-Reply-To: <cd0a5694-fd6a-ffe5-2364-14cc1e569a3f@linux.ibm.com>

On 3/4/22 8:14 PM, Peter Bergner wrote:
> On 3/4/22 11:33 AM, Peter Bergner wrote:
>>> Ok pushed to trunk.  I haven't determined yet whether we need this on GCC 11 yet.
>>> I'll check on that and report back.  Thanks!
>>
>> I've confirmed that GCC 11 fails the same way and that the backported patch
>> fixes the issue there too.  Ok for GCC 11 assuming my full regression testing
>> is clean?
>>
>> GCC 10 has the same checking code, so it looks to need the backport as well.
>> I'll go ahead and backport and regression test it there too.
> 
> The backports to GCC 11 and GCC 10 bootstrapped and regtested with no regressions.
> Ok for the GCC 11 and GCC 10 release branches after a day or two of baking on
> trunk?

Ping.

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?

Peter




       reply	other threads:[~2022-03-15 19:49 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 [this message]
2022-03-16 12:33           ` [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm, ieee}longdouble " Segher Boessenkool
2022-03-18 19:19             ` [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble " Peter Bergner

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=8c003ae0-8bf7-62f1-2760-0340e05502df@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).