public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot 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: Sun, 19 May 2024 19:46:58 +0000 [thread overview] Message-ID: <bug-26566-131-huQa4dKg4x@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 #10 from Florian Weimer <fweimer at redhat dot com> --- Please check the disassembly of _Unwind_RaiseException in libgcc_s.so.1 to check whether it contains code to save vector registers, perhaps like this: gdb -batch -ex "disassemble/s _Unwind_RaiseException" /lib64/libgcc_s.so.1 If GCC defaults to POWER8 instructions, it looks like this: Dump of assembler code for function _Unwind_RaiseException: ../../../libgcc/unwind.inc: 87 { 0x000000000000c610 <+0>: addis r2,r12,3 0x000000000000c614 <+4>: addi r2,r2,-18704 0x000000000000c618 <+8>: mr r0,r1 0x000000000000c61c <+12>: stdu r1,-4096(r1) 0x000000000000c620 <+16>: stdu r0,-528(r1) 0x000000000000c624 <+20>: mflr r0 0x000000000000c628 <+24>: stfd f14,4480(r1) 0x000000000000c62c <+28>: stfd f15,4488(r1) 0x000000000000c630 <+32>: stfd f16,4496(r1) 0x000000000000c634 <+36>: stfd f17,4504(r1) 0x000000000000c638 <+40>: stfd f18,4512(r1) […] 0x000000000000c6cc <+188>: beq 0xc6d4 <_Unwind_RaiseException+196> 0x000000000000c6d0 <+192>: std r2,4648(r1) 88 struct _Unwind_Context this_context, cur_context; 89 _Unwind_Reason_Code code; 90 unsigned long frames; 91 92 /* Set up this_context to describe the current stack frame. */ 93 uw_init_context (&this_context); 0x000000000000c6d4 <+196>: mfcr r0 0x000000000000c6d8 <+200>: mflr r5 0x000000000000c6dc <+204>: addi r27,r1,3000 0x000000000000c6e0 <+208>: addi r4,r1,4624 0x000000000000c6e4 <+212>: mr r28,r3 0x000000000000c6e8 <+216>: mr r3,r27 0x000000000000c6ec <+220>: addi r30,r1,1920 0x000000000000c6f0 <+224>: addi r29,r1,32 0x000000000000c6f4 <+228>: stw r0,4088(r1) 0x000000000000c6f8 <+232>: stw r0,4096(r1) 0x000000000000c6fc <+236>: stw r0,4104(r1) 0x000000000000c700 <+240>: li r0,4144 0x000000000000c704 <+244>: stvx v20,r1,r0 0x000000000000c708 <+248>: li r0,4160 0x000000000000c70c <+252>: stvx v21,r1,r0 […] -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-05-19 19:46 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 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 [this message] 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-huQa4dKg4x@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: 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).