public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102107] protocol register (r12) corrupted before a tail call Date: Mon, 30 Aug 2021 19:58:34 +0000 [thread overview] Message-ID: <bug-102107-4-UZEwcYFcDI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102107-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102107 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org --- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> --- I get (-mcpu=power10 -mabi=elfv2 -O2): .L2: ld 9,0(30) # 59 [c=8 l=4] *movdi_internal64/1 addi 1,1,112 # 124 [c=4 l=4] *adddi3/1 .cfi_def_cfa_offset 0 li 3,0 # 63 [c=4 l=4] *movdi_internal64/3 ld 0,16(1) # 125 [c=8 l=4] *movdi_internal64/1 ld 31,-8(1) # 129 [c=8 l=4] *movdi_internal64/1 ld 12,0(9) # 62 [c=8 l=4] *movdi_internal64/1 addi 9,9,8 # 60 [c=4 l=4] *adddi3/1 std 9,0(30) # 61 [c=4 l=4] *movdi_internal64/0 ld 30,-16(1) # 128 [c=8 l=4] *movdi_internal64/1 mtlr 0 # 127 [c=4 l=4] *movdi_internal64/23 .cfi_restore 65 mtctr 12 # 103 [c=4 l=4] *movdi_internal64/23 lwz 12,8(1) # 126 [c=8 l=4] *movsi_internal1/2 mtcrf 8,12 # 130 [c=4 l=4] *mtcrfsi .cfi_restore 72 .cfi_restore 31 .cfi_restore 30 bctr # 66 [c=4 l=4] *sibcall_value_aixdi/1 This looks just fine. What is wrong with your build?
next prev parent reply other threads:[~2021-08-30 19:58 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-27 20:54 [Bug target/102107] New: " pc at us dot ibm.com 2021-08-27 21:01 ` [Bug target/102107] " pc at us dot ibm.com 2021-08-27 21:03 ` pc at us dot ibm.com 2021-08-28 21:56 ` pc at us dot ibm.com 2021-08-28 22:33 ` pc at us dot ibm.com 2021-08-30 16:24 ` pc at us dot ibm.com 2021-08-30 19:58 ` segher at gcc dot gnu.org [this message] 2021-08-30 20:19 ` wschmidt at gcc dot gnu.org 2021-08-30 20:42 ` pc at us dot ibm.com 2021-08-30 22:49 ` segher at gcc dot gnu.org 2021-08-30 23:42 ` segher at gcc dot gnu.org 2021-08-31 13:20 ` pc at us dot ibm.com 2021-08-31 15:22 ` segher at gcc dot gnu.org 2021-08-31 17:43 ` segher at gcc dot gnu.org 2021-09-01 17:50 ` segher at gcc dot gnu.org 2021-09-03 21:05 ` cvs-commit at gcc dot gnu.org 2021-09-03 21:08 ` segher at gcc dot gnu.org 2021-09-08 13:30 ` cvs-commit at gcc dot gnu.org 2021-09-21 23:45 ` cvs-commit at gcc dot gnu.org 2021-09-21 23:45 ` cvs-commit at gcc dot gnu.org 2021-09-21 23:47 ` cvs-commit at gcc dot gnu.org 2021-09-21 23:47 ` cvs-commit at gcc dot gnu.org 2021-09-21 23:53 ` segher at gcc dot gnu.org 2021-09-27 22:26 ` pc at us dot ibm.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-102107-4-UZEwcYFcDI@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: 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).