public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmatti at linux dot vnet.ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/26566] nptl/tst-thread-exit-clobber fails on powerpc/powerpc64 with GCC 10.2
Date: Wed, 08 May 2024 06:15:04 +0000	[thread overview]
Message-ID: <bug-26566-131-NOXhPgNgzl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26566-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26566

--- Comment #5 from Manjunath S Matti <mmatti at linux dot vnet.ibm.com> ---
I have some more info here:

I have run make check on both x86 and PPC64le, this particular testcase is
marked as
UNSUPPORTED: nptl/tst-thread-exit-clobber


Also this testcase compares 2 doubles is this ok ?

106 __attribute__ ((noinline, noclone, weak))
107 void
108 check_magic (int index, double value)
109 {
110   switch (index)
111     {
112     case 0:
113       TEST_VERIFY (value == magic_values_double.v0); -> here
114       break;

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-05-08  6:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 13:52 [Bug nptl/26566] New: " msc at linux dot ibm.com
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 [this message]
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-NOXhPgNgzl@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).