public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94556] New: [10 Regression] FAIL: nptl/tst-thread-exit-clobber Date: Fri, 10 Apr 2020 20:42:11 +0000 [thread overview] Message-ID: <bug-94556-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94556 Bug ID: 94556 Summary: [10 Regression] FAIL: nptl/tst-thread-exit-clobber Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com Target Milestone: --- Target: x86-64 On Linux/x32, GCC 10.0.1 20200324 caused FAIL: nptl/tst-thread-exit-clobber [hjl@gnu-cfl-2 build-x86_64-linux]$ nptl/tst-thread-exit-clobber --direct info: unsigned int, direct pthread_exit call info: double, direct pthread_exit call error: tst-thread-exit-clobber.cc:119: not true: value == magic_values_double.v2 info: unsigned int, indirect pthread_exit call info: double, indirect pthread_exit call error: 1 test failures [hjl@gnu-cfl-2 build-x86_64-linux]$ in tests on glibc master branch. GCC 9.3 is OK.
next reply other threads:[~2020-04-10 20:42 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-10 20:42 hjl.tools at gmail dot com [this message] 2020-04-10 21:39 ` [Bug target/94556] " hjl.tools at gmail dot com 2020-04-10 21:46 ` hjl.tools at gmail dot com 2020-04-10 22:38 ` hjl.tools at gmail dot com 2020-04-10 22:39 ` hjl.tools at gmail dot com 2020-04-12 14:30 ` hjl.tools at gmail dot com 2020-04-12 17:19 ` hjl.tools at gmail dot com 2020-04-13 11:26 ` cvs-commit at gcc dot gnu.org 2020-04-13 19:38 ` [Bug target/94556] " law at redhat dot com 2020-04-14 6:47 ` rguenth at gcc dot gnu.org 2020-04-20 13:05 ` cvs-commit at gcc dot gnu.org 2020-04-20 13:05 ` cvs-commit at gcc dot gnu.org 2020-04-20 13:07 ` hjl.tools at gmail dot com
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=bug-94556-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).