From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: 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>
Subject: Re: [BACKPORT] Apply fix for PR libgcc/97643 to gcc 10 branch
Date: Wed, 20 Jan 2021 20:28:57 -0500 [thread overview]
Message-ID: <20210121012857.GA16413@ibm-toto.the-meissners.org> (raw)
In-Reply-To: <20210121004614.GI30983@gate.crashing.org>
On Wed, Jan 20, 2021 at 06:46:14PM -0600, Segher Boessenkool wrote:
> On Wed, Jan 20, 2021 at 06:38:37PM -0500, Michael Meissner wrote:
> > This patch takes the fix that was applied to the trunk on December 3rd, and it
> > applies it to the GCC 10 branch.
>
> > PR libgcc/97543, PR libgcc/97643
> > Backport from trunk.
> >
> > 2020-12-03 Michael Meissner <meissner@linux.ibm.com>
> >
> > * config/rs6000/t-linux (IBM128_STATIC_OBJS): New make variable.
> > (IBM128_SHARED_OBJS): New make variable.
> > (IBM128_OBJS): New make variable. Set all objects to use the
> > explicit IBM format, and disable gnu attributes.
> > (IBM128_CFLAGS): New make variable.
> > (gcc_s_compile): Add -mno-gnu-attribute to all shared library
> > modules.
>
> Okay for 10. Thanks!
>
> Is there a reason we do not have that testcase in the testsuite, btw?
In order to test it you need to build a compiler + toolchain where the default
long double is 64-bits. So it is kind of hard to put in a test for it, since
it was a bug in how libgcc was built with a compiler that defaults to 64-bit
long double.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.ibm.com, phone: +1 (978) 899-4797
next prev parent reply other threads:[~2021-01-21 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 23:38 Michael Meissner
2021-01-21 0:46 ` Segher Boessenkool
2021-01-21 1:28 ` Michael Meissner [this message]
2021-01-21 21:38 ` 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=20210121012857.GA16413@ibm-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=segher@kernel.crashing.org \
--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).