From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH, V3] PR target/99708- Define __SIZEOF_FLOAT128__ and __SIZEOF_IBM128__
Date: Fri, 11 Mar 2022 17:51:05 -0500 [thread overview]
Message-ID: <YivSWSpw9C9fOReu@toto.the-meissners.org> (raw)
In-Reply-To: <20220311205123.GA614@gate.crashing.org>
On Fri, Mar 11, 2022 at 02:51:23PM -0600, Segher Boessenkool wrote:
> On Fri, Mar 11, 2022 at 08:42:27PM +0000, Joseph Myers wrote:
> > The version of this patch applied to GCC 10 branch (commit
> > 641b407763ecfee5d4ac86d8ffe9eb1eeea5fd10) has broken the glibc build for
> > powerpc64le-linux-gnu (it's fine with GCC 11 branch and master, just GCC
> > 10 branch is broken)
>
> Mike, please revert it then?
Ok, I will revert both the GCC 11 and GCC 10 backport once I make sure the fix
builds. Sorry about that. Obviously, we will want to backport whatever we do
shortly to the older branches.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
next prev parent reply other threads:[~2022-03-11 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 23:03 Michael Meissner
2022-02-16 23:43 ` Segher Boessenkool
2022-03-11 20:42 ` Joseph Myers
2022-03-11 20:51 ` Segher Boessenkool
2022-03-11 20:57 ` Jakub Jelinek
2022-03-11 21:07 ` Segher Boessenkool
2022-03-12 0:48 ` Michael Meissner
2022-03-11 22:51 ` Michael Meissner [this message]
2022-03-12 15:59 ` 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=YivSWSpw9C9fOReu@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=joseph@codesourcery.com \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.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).