From: Jakub Jelinek <jakub@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Fix iseqsig for _FloatN and _FloatNx in C++ with GCC 13
Date: Thu, 29 Sep 2022 18:15:31 +0200 [thread overview]
Message-ID: <YzXEow9rjrF6Uhw6@tucnak> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2209290013040.449237@digraph.polyomino.org.uk>
On Thu, Sep 29, 2022 at 12:15:09AM +0000, Joseph Myers wrote:
> Tested with build-many-glibcs.py glibcs build for aarch64-linux-gnu
> ia64-linux-gnu i686-linux-gnu mips-linux-gnu mips64-linux-gnu-n32
> powerpc-linux-gnu powerpc64le-linux-gnu x86_64-linux-gnu. Note that
> there is an ICE building the glibc testsuite for x86_64 / i686 / ia64
> <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107080>, which will need
> to be resolved to complete testing this patch.
I've posted a fix for that.
> I am seeking review of this patch, not applying it as a math
> maintainer. Also, full testing will need GCC bug 107080 (test reduced
> from an ICE building the glibc testcase modified by this patch) to be
> fixed.
LGTM.
Reviewed-by: Jakub Jelinek <jakub@redhat.com>
Jakub
prev parent reply other threads:[~2022-09-29 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 0:15 Joseph Myers
2022-09-29 16:15 ` Jakub Jelinek [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=YzXEow9rjrF6Uhw6@tucnak \
--to=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).