* Re: [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble [PR104208, PR87496] [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 0 siblings, 1 reply; 3+ messages in thread From: Peter Bergner @ 2022-03-15 19:49 UTC (permalink / raw) To: David Edelsohn, Segher Boessenkool Cc: Jakub Jelinek, Florian Weimer, GCC Patches 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm, ieee}longdouble [PR104208, PR87496] 2022-03-15 19:49 ` [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble [PR104208, PR87496] Peter Bergner @ 2022-03-16 12:33 ` Segher Boessenkool 2022-03-18 19:19 ` [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble " Peter Bergner 0 siblings, 1 reply; 3+ messages in thread From: Segher Boessenkool @ 2022-03-16 12:33 UTC (permalink / raw) To: Peter Bergner; +Cc: David Edelsohn, Jakub Jelinek, Florian Weimer, GCC Patches On Tue, Mar 15, 2022 at 02:49:39PM -0500, Peter Bergner wrote: > 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? If you can confirm it fixes the glibc build error on 11 and 10 as well, then yes please. Thanks! Segher ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble [PR104208, PR87496] 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 0 siblings, 0 replies; 3+ messages in thread From: Peter Bergner @ 2022-03-18 19:19 UTC (permalink / raw) To: Segher Boessenkool Cc: David Edelsohn, Jakub Jelinek, Florian Weimer, GCC Patches 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-03-18 19:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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 ` [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble [PR104208, PR87496] 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 ` [PATCH] rs6000: Allow using -mlong-double-64 after -mabi={ibm,ieee}longdouble " Peter Bergner
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).