public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msc at linux dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/26566] New: nptl/tst-thread-exit-clobber fails on powerpc/powerpc64 with GCC 10.2
Date: Wed, 02 Sep 2020 13:52:46 +0000 [thread overview]
Message-ID: <bug-26566-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26566
Bug ID: 26566
Summary: nptl/tst-thread-exit-clobber fails on
powerpc/powerpc64 with GCC 10.2
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: nptl
Assignee: unassigned at sourceware dot org
Reporter: msc at linux dot ibm.com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
FAIL: nptl/tst-thread-exit-clobber
original exit status 1
info: unsigned int, direct pthread_exit call
error: tst-thread-exit-clobber.cc:125: not true: value ==
magic_values_double.v4
error: tst-thread-exit-clobber.cc:122: not true: value ==
magic_values_double.v3
error: tst-thread-exit-clobber.cc:119: not true: value ==
magic_values_double.v2
error: tst-thread-exit-clobber.cc:116: not true: value ==
magic_values_double.v1
error: tst-thread-exit-clobber.cc:113: not true: value ==
magic_values_double.v0
error: 5 test failures
I can only reproduce this error on ppc and ppc64, not ppc64le. Also, it works
with GCC 9.3, but fails with GCC 10.2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-09-02 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 13:52 msc at linux dot ibm.com [this message]
2020-09-04 22:11 ` [Bug nptl/26566] " adhemerval.zanella at linaro dot org
2020-09-15 15:10 ` tuliom at ascii dot art.br
2024-01-22 15:51 ` carlos at redhat dot com
2024-03-21 12:59 ` mmatti at linux dot vnet.ibm.com
2024-04-24 5:49 ` mmatti at linux dot vnet.ibm.com
2024-05-08 6:15 ` mmatti at linux dot vnet.ibm.com
2024-05-08 6:16 ` mmatti at linux dot vnet.ibm.com
2024-05-08 9:58 ` fweimer at redhat dot com
2024-05-17 14:08 ` jeevitha at linux dot ibm.com
2024-05-17 16:28 ` fweimer at redhat dot com
2024-05-19 18:21 ` jskumari at linux dot ibm.com
2024-05-19 19:46 ` fweimer at redhat dot com
2024-05-21 7:43 ` jeevitha at linux dot ibm.com
2024-05-21 7:53 ` fweimer at redhat 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-26566-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).