public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109889] [13/14 Regression] Segfault in __run_exit_handlers since r13-5309-gc3c6c307792026
Date: Wed, 17 May 2023 11:25:20 +0000 [thread overview]
Message-ID: <bug-109889-4-ahGvh4ZUdp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109889-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109889
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
r2 is the toc pointer, so having it 0 is weird.
Looking at glibc-2.36-10.fc37 (not sure if you are using a different one), I
see
000000000005b560 <__run_exit_handlers>:
5b560: 21 00 4c 3c addis r2,r12,33
5b564: a0 b9 42 38 addi r2,r2,-18016
...
5b5a8: 18 00 41 f8 std r2,24(r1)
so wonder what x/1gx $r1+24 is. Most likely some call from that function
didn't restore r2 properly?
Though, I believe in PowerPC ELFv2 it is the caller's responsibility to restore
it
and that is why it has the nops after bl (in case the call is guaranteed to be
into code with the same TOC) and ld r2,24(r1) otherwise.
next prev parent reply other threads:[~2023-05-17 11:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 11:10 [Bug libstdc++/109889] New: " redi at gcc dot gnu.org
2023-05-17 11:17 ` [Bug libstdc++/109889] " redi at gcc dot gnu.org
2023-05-17 11:25 ` jakub at gcc dot gnu.org [this message]
2023-05-17 11:26 ` redi at gcc dot gnu.org
2023-05-17 11:30 ` redi at gcc dot gnu.org
2023-05-17 15:04 ` tuliom at ascii dot art.br
2023-05-17 15:10 ` tuliom at ascii dot art.br
2023-05-17 15:50 ` redi at gcc dot gnu.org
2023-05-17 15:57 ` redi at gcc dot gnu.org
2023-05-17 15:58 ` redi at gcc dot gnu.org
2023-05-17 15:59 ` redi at gcc dot gnu.org
2023-05-17 19:38 ` rguenth at gcc dot gnu.org
2023-05-19 12:49 ` redi at gcc dot gnu.org
2023-05-24 12:04 ` redi at gcc dot gnu.org
2023-07-27 9:26 ` rguenth at gcc dot gnu.org
2024-05-21 9:15 ` [Bug libstdc++/109889] [13/14/15 " jakub at gcc dot gnu.org
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-109889-4-ahGvh4ZUdp@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).