From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6B873384AB44; Fri, 17 May 2024 16:28:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6B873384AB44 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1715963300; bh=dyUx7d+IYGDbpqftFa0I8w7clxuInOYZ1DcT6RRND0A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dSZOpqgXP/zaGlyW2pMIYhABEh3gOTB2sAQ4K9CvENy766ectdBK3NBkbH23iKLjF BKwFCo1hW6K+WucRVIaEgj8NcSPzx6eVt9Y1gLjj0aj3eqQCQXDltanKOLQvtFAx+U S8RDuVW6WF1ovr3ncQS9m1BvKKRmH0WdEG5RPx/M= 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: Fri, 17 May 2024 16:28:19 +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: 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 --- Comment #8 from Florian Weimer --- I suspect this happens if the libgcc unwinder has been built in such a way = that it doesn't require a CPU with VSX support. In that case, it's not safe to b= uild code with -mcpu=3Dpower8 if it catches exceptions, as the test shows. I really don't think this is a glibc bug. The libgcc unwinder should have conditional vector register processing even if built with -mno-vsx. --=20 You are receiving this mail because: You are on the CC list for the bug.=