From: Joseph Myers <joseph@codesourcery.com>
To: Vasee Vinayagamoorthy <vaseeharan.vinayagamoorthy@arm.com>
Cc: Khem Raj via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Fix build with GCC 10 when long double = double [committed]
Date: Mon, 4 May 2020 20:26:06 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2005042023200.22972@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20200504105147.GA6183@e109781-lin.cambridge.arm.com>
On Mon, 4 May 2020, Vasee Vinayagamoorthy wrote:
> Hi Joseph,
>
> I also think that we need this patch backported to glibc 2.31 branch
> because we are seeing failures for arm-none-linux-gnueabihf target when
> building GCC 10 with glibc 2.31:
Anyone who wishes to build older glibc versions with newer compilers
should feel free to cherry-pick relevant commits to the release branches
following the usual release-branch process
<https://sourceware.org/glibc/wiki/Release#General_policy>, discussing the
proposed changes on libc-stable as necessary. I don't tend to backport
non-regression fixes myself unless I have an actual use for the fix on an
older branch.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2020-05-04 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 22:58 Joseph Myers
2020-03-26 6:34 ` Khem Raj
2020-05-04 10:51 ` Vasee Vinayagamoorthy
2020-05-04 20:26 ` Joseph Myers [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=alpine.DEB.2.21.2005042023200.22972@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=vaseeharan.vinayagamoorthy@arm.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).