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/115360] cmse_nonsecure_call wrapper on arm missing STT_FUNCTION Date: Thu, 06 Jun 2024 15:03:20 +0000 [thread overview] Message-ID: <bug-115360-4-P6TPy79bma@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115360-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115360 --- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andre Simoes Dias Vieira <avieira@gcc.gnu.org>: https://gcc.gnu.org/g:c559353af49fe5743d226ac3112a285b27a50f6a commit r15-1073-gc559353af49fe5743d226ac3112a285b27a50f6a Author: Andre Vieira <andre.simoesdiasvieira@arm.com> Date: Thu Jun 6 16:02:50 2024 +0100 arm: Add .type and .size to __gnu_cmse_nonsecure_call [PR115360] This patch adds missing assembly directives to the CMSE library wrapper to call functions with attribute cmse_nonsecure_call. Without the .type directive the linker will fail to produce the correct veneer if a call to this wrapper function is to far from the wrapper itself. The .size was added for completeness, though we don't necessarily have a usecase for it. libgcc/ChangeLog: PR target/115360 * config/arm/cmse_nonsecure_call.S: Add .type and .size directives.
next prev parent reply other threads:[~2024-06-06 15:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-05 15:11 [Bug target/115360] New: cmse_nonsecure_call wrapper " avieira at gcc dot gnu.org 2024-06-05 15:14 ` [Bug target/115360] cmse_nonsecure_call wrapper on arm " rearnsha at gcc dot gnu.org 2024-06-06 15:03 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-12 14:09 ` cvs-commit at gcc dot gnu.org 2024-06-12 14:11 ` cvs-commit at gcc dot gnu.org 2024-06-12 14:12 ` cvs-commit at gcc dot gnu.org 2024-06-12 14:13 ` cvs-commit at gcc dot gnu.org 2024-06-12 14:15 ` avieira 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-115360-4-P6TPy79bma@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).