From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 21DF7384AB47; Wed, 8 May 2024 09:58:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 21DF7384AB47 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1715162329; bh=Ilon12v0MkbHnnofd6aSmQzWfcBtpOBGurUcgtOCRro=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VHFGelVdbtBPSeMLwZeMM7Ou31jzRpafnqKfLEnbgkq9rNbXJGKo83oJyzYId/Yno c/uMuC3b4D5FAsiROt2VIUKoq/H7xgEu8jTwvb6ohCjAG9KBcRMLuWunvTzULXvnXR dNrtP9jctoLc+EExlOJY3m4kQQ8bjqP0yjmt0iL4= From: "fweimer at redhat dot com" 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 09:58:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D26566 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #6 from Florian Weimer --- (In reply to Manjunath S Matti from comment #5) > I have some more info here: >=20 > I have run make check on both x86 and PPC64le, this particular testcase is > marked as > UNSUPPORTED: nptl/tst-thread-exit-clobber I think this happens because it's a C++ tested, and you either do not have a g++ installed, or libstdc++-static is missing (yes, we should probably fixed that, and not disable all C++ tests if C++ static linking is unsupported). > Also this testcase compares 2 doubles is this ok ? >=20 > 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 =3D=3D magic_values_double.v0); -> here > 114 break; Are you asking because of a general rule that says not to compare floating point numbers for equality? In this case, we want to make sure that the test case preserves the bit pattern exactly. --=20 You are receiving this mail because: You are on the CC list for the bug.=