public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104894] [11/12 Regression] ICE with -fno-plt -mcpu=power10 on PowerPC64 LE Linux Date: Tue, 12 Apr 2022 20:24:25 +0000 [thread overview] Message-ID: <bug-104894-4-OONMzYpTfk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104894-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104894 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Peter Bergner <bergner@gcc.gnu.org>: https://gcc.gnu.org/g:5ede37c0f274f0de19afd662588891e32b60f705 commit r11-9836-g5ede37c0f274f0de19afd662588891e32b60f705 Author: Peter Bergner <bergner@linux.ibm.com> Date: Tue Apr 12 14:08:53 2022 -0500 rs6000: Handle pcrel sibcalls to longcall functions [PR104894] Before PCREL in POWER10, we were not allowed to perform sibcalls to longcall functions since callee's return would skip the TOC restore in the caller. However, with PCREL we can now safely perform a sibling call to longcall functions. The problem with the current code is that pcrel sibcall branches to a PLT stub label even though -fno-plt was used. The solution here is to check for a pcrel longcall and emit an inline plt stub in that case. 2022-04-11 Peter Bergner <bergner@linux.ibm.com> gcc/ PR target/104894 * config/rs6000/rs6000.c (rs6000_sibcall_aix): Handle pcrel sibcalls to longcall functions. gcc/testsuite/ PR target/104894 * gcc.target/powerpc/pr104894.c: New test. * gcc.target/powerpc/pr104894-2.c: New test. (cherry picked from commit d74c4c6a1b4956b5cd9b2a770bb7261836fa1289)
next prev parent reply other threads:[~2022-04-12 20:24 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-12 14:45 [Bug c/104894] New: [ppc64le] gcc11 ICE with -fno-plt rafaelcfsousa at ibm dot com 2022-03-13 7:36 ` [Bug target/104894] [11/12 Regression] ICE with -fno-plt -mcpu=power10 on PowerPC64 LE Linux pinskia at gcc dot gnu.org 2022-03-15 2:28 ` amodra at gmail dot com 2022-03-15 9:02 ` jakub at gcc dot gnu.org 2022-03-22 21:44 ` bergner at gcc dot gnu.org 2022-03-23 1:11 ` amodra at gmail dot com 2022-03-23 12:54 ` rguenth at gcc dot gnu.org 2022-03-24 21:33 ` bergner at gcc dot gnu.org 2022-03-24 23:55 ` amodra at gmail dot com 2022-03-25 0:02 ` amodra at gmail dot com 2022-04-04 22:13 ` bergner at gcc dot gnu.org 2022-04-05 22:07 ` bergner at gcc dot gnu.org 2022-04-11 22:02 ` cvs-commit at gcc dot gnu.org 2022-04-12 20:24 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-12 20:32 ` bergner 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-104894-4-OONMzYpTfk@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).