public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pc at us dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102107] protocol register (r12) corrupted before a tail call Date: Tue, 31 Aug 2021 13:20:32 +0000 [thread overview] Message-ID: <bug-102107-4-Z8O1ChFWnD@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 --- Comment #11 from Paul Clarke <pc at us dot ibm.com> --- This does produce the issue for me: -- $ git checkout remotes/vendors/ibm/gcc-11-branch gcc-AT $ mkdir gcc-AT-build $ cd gcc-AT-build $ ../gcc-AT/configure --enable-languages=c,c++ --disable-libada --disable-libsanitizer --disable-libssp --disable-libgomp --disable-libvtv --disable-nls --prefix=/home/pc/gcc-AT-install $ make $ make install $ ~/gcc-AT-install/bin/gcc -S -O3 -mcpu=power10 -fverbose-asm r12test2.c $ grep --before-context=15 bctr r12test2.s mtctr 12 # func, func # r12test2.c:3030: } lwz 12,8(1) #, # r12test2.c:3013: ++*p_format; addi 9,9,1 # tmp251, *p_format_31(D), std 9,0(31) # *p_format_31(D), tmp251 # r12test2.c:3030: } ld 31,-8(1) #, mtcrf 8,12 #, .cfi_restore 72 .cfi_restore 31 .cfi_restore 30 .cfi_restore 28 .cfi_restore 27 # r12test2.c:3014: return (*func)(); bctr # func --
next prev parent reply other threads:[~2021-08-31 13:20 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 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 [this message] 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-Z8O1ChFWnD@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).