From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-stable@sourceware.org, WANG Xuerui <xen0n@gentoo.org>,
toolchain@gentoo.org
Subject: [Disregard my previous mail] Re: Please backport some GCC 13 build fixes
Date: Sun, 27 Nov 2022 15:35:56 +0100 [thread overview]
Message-ID: <3199754.aeNJFYEL58@pinacolada> (raw)
In-Reply-To: <cbebfe38-fec9-fa35-a748-5e3cfe8bb0ce@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
Am Montag, 21. November 2022, 21:37:18 CET schrieb Joseph Myers:
> On Sat, 19 Nov 2022, Andreas K. Huettel via Libc-stable wrote:
>
> > > * 3e5760fcb4 ("Update _FloatN header support for C++ in GCC 13")
> > > * ba70f69598 ("Fix iseqsig for _FloatN and _FloatNx in C++ with GCC 13")
> > > * f66780ba46 ("Fix build with GCC 13 _FloatN, _FloatNx built-in
> > > functions")
> >
> > FWIW, I added these three commits to our 2.36 and got some FP test failures
> > requiring distinct changes in ulps.
>
> These aren't meant to change the code generated for glibc (with any given
> GCC version that worked for building glibc before those changes, so GCC 12
> or before) at all, so it would be a good idea to investigate why the
> generated code changed.
My apologies; this was *not* caused by the three commits listed above.
So, from my point of view there are no problems at all with backporting them.
The changes which broke the tests must have crept into the/our release branch
earlier. Searching.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2022-11-27 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 18:55 WANG Xuerui
2022-11-19 20:09 ` Andreas K. Huettel
2022-11-21 20:37 ` Joseph Myers
2022-11-27 14:35 ` Andreas K. Huettel [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=3199754.aeNJFYEL58@pinacolada \
--to=dilfridge@gentoo.org \
--cc=joseph@codesourcery.com \
--cc=libc-stable@sourceware.org \
--cc=toolchain@gentoo.org \
--cc=xen0n@gentoo.org \
/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).