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/113780] [ARM] Incorrect indirect tailcall generated for PAC-enabled function.
Date: Fri, 16 Feb 2024 04:14:32 +0000 [thread overview]
Message-ID: <bug-113780-4-XbfbRpR66D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113780-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113780
--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tejas Belagod <belagod@gcc.gnu.org>:
https://gcc.gnu.org/g:f436a2ab6ad15968275c9bbf3bd56647e5559e68
commit r14-9022-gf436a2ab6ad15968275c9bbf3bd56647e5559e68
Author: Tejas Belagod <tejas.belagod@arm.com>
Date: Thu Jan 25 16:05:36 2024 +0530
Arm: Fix incorrect tailcall-generation for indirect calls [PR113780]
This patch fixes a bug that causes indirect calls in PAC-enabled functions
to be tailcalled incorrectly when all argument registers R0-R3 are used.
2024-02-07 Tejas Belagod <tejas.belagod@arm.com>
PR target/113780
* config/arm/arm.cc (arm_function_ok_for_sibcall): Don't allow
tailcalls
for indirect calls with 4 or more arguments in pac-enabled
functions.
* lib/target-supports.exp (v8_1m_main_pacbti): Add
__ARM_FEATURE_PAUTH.
* gcc.target/arm/pac-sibcall.c: New.
next prev parent reply other threads:[~2024-02-16 4:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 4:55 [Bug target/113780] New: " belagod at gcc dot gnu.org
2024-02-06 4:56 ` [Bug target/113780] " belagod at gcc dot gnu.org
2024-02-06 4:57 ` belagod at gcc dot gnu.org
2024-02-06 4:58 ` belagod at gcc dot gnu.org
2024-02-08 11:17 ` rearnsha at gcc dot gnu.org
2024-02-16 4:14 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-16 4:18 ` belagod 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-113780-4-XbfbRpR66D@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).