From: Michael Meissner <meissner@linux.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.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] Allow other languages to change long double format on PowerPC
Date: Wed, 12 Jan 2022 12:56:18 -0500 [thread overview]
Message-ID: <Yd8WQrKHK9KgGTje@toto.the-meissners.org> (raw)
In-Reply-To: <20220112175004.GM2646553@tucnak>
On Wed, Jan 12, 2022 at 06:50:04PM +0100, Jakub Jelinek wrote:
> On Wed, Jan 12, 2022 at 12:46:16PM -0500, Michael Meissner via Gcc-patches wrote:
> > Allow other languages to change long double format on PowerPC.
> >
> > With Fortran adding support for changing the long double format, this
> > patch removes the code that only allowed C/C++ to change the long double
> > format for GLIBC 2.32 and later without a warning.
> >
> > I have bootstraped the compiler with this change and there where no
> > regressesion. In addition, I have applied it to the power-ieee128 branch where
> > the work is being done to add support for both types of 128-bit floating point
> > on PowerPC. If I build a compiler from that branch, I can change the 128-bit
> > floating point format at compile time.
> >
> > Can I check this patch into the trunk GCC compiler?
> >
> > gcc/
> > 2022-01-12 Michael Meissner <meissner@the-meissners.org>
> >
> > * config/rs6000/rs6000.c (rs6000_option_override_internal): Remove
> > checks for only C/C++ front ends before allowing the long double
> > format to change without a warning.
>
> This is already on the trunk, I've merged the power-ieee128 branch changes
> into trunk yesterday (r12-6491 through r12-6508 commits inclusive).
> This patch in particular as r12-6503-g7d8011fa00fca283003c84e23a8ca66286f83dfa.
Thanks. I didn't notice that the patches had been merged into the trunk.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
prev parent reply other threads:[~2022-01-12 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 17:46 Michael Meissner
2022-01-12 17:50 ` Jakub Jelinek
2022-01-12 17:56 ` Michael Meissner [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=Yd8WQrKHK9KgGTje@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=jakub@redhat.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).