public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113780] New: [ARM] Incorrect indirect tailcall generated for PAC-enabled function.
Date: Tue, 06 Feb 2024 04:55:22 +0000	[thread overview]
Message-ID: <bug-113780-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113780

            Bug ID: 113780
           Summary: [ARM] Incorrect indirect tailcall generated for
                    PAC-enabled function.
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: belagod at gcc dot gnu.org
  Target Milestone: ---

For this piece of code:

void fail(void (*f)(int, int, int, int))
{
  f(1, 2, 3, 4);
}

compiled with -mcpu=cortex-m85 -mbranch-protection=pac-ret+leaf -O2 on trunk,
it generates:

fail:
        pac     ip, lr, sp
        movs    r3, #4
        movs    r2, #3
        movs    r1, #2
        movs    r0, #1
        push    {ip, lr}
        pop     {ip, lr}
        aut     ip, lr, sp
        bx      ip  @ indirect register sibling call

             reply	other threads:[~2024-02-06  4:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06  4:55 belagod at gcc dot gnu.org [this message]
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
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@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).