From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org, gcc@gcc.gnu.org
Subject: glibc nptl/tst-cancelx18 test fails with GCC 9.2 on Arm 32-bit
Date: Thu, 05 Sep 2019 15:24:57 +0200 [thread overview]
Message-ID: <87blvykh92.fsf@oldenburg2.str.redhat.com> (raw)
I think since the upgrade to GCC 9.2 in Fedora, the glibc test
nptl/tst-cancelx18 (which is built with -fexceptions) fails on the Arm
32-bit architecture (and only there). I'm not 100% certain that it's
caused by the GCC update, but the patterns of failures and passes
strongly suggests that.
I don't know the proper name for the exact 32-bit Arm variant Fedora
uses. Its armv7 with hardware floating point, I think.
I'm trying to get a lab machine to debug this further, but in the past,
that was difficult.
Thanks,
Florian
next reply other threads:[~2019-09-05 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 13:24 Florian Weimer [this message]
2019-09-05 13:36 ` glibc nptl/tst-cancelx18 test fails with GCC 9.2 on Arm 32-bit Florian Weimer
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blvykh92.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--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).