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/97638] aarch64: bti c is missing at function entry with branch-protection Date: Mon, 02 Nov 2020 15:53:21 +0000 [thread overview] Message-ID: <bug-97638-4-cZEvCRlvsI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97638-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97638 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Sudakshina Das <sudi@gcc.gnu.org>: https://gcc.gnu.org/g:ce99142c11b8090105cbf2aa853262f6d9abc0d3 commit r11-4615-gce99142c11b8090105cbf2aa853262f6d9abc0d3 Author: Sudakshina Das <sudi.das@arm.com> Date: Mon Nov 2 15:52:22 2020 +0000 [PATCH] aarch64: Fix PR97638 Currently the testcase in the patch was failing to produce a 'bti c' at the beginning of the function. This was because in aarch64_pac_insn_p, we were wrongly returning at the first check! 2020-10-30 Sudakshina Das <sudi.das@arm.com> gcc/ChangeLog: PR target/97638 * config/aarch64/aarch64-bti-insert.c (aarch64_pac_insn_p): Update return value on INSN_P check. gcc/testsuite/ChangeLog: PR target/97638 * gcc.target/aarch64/pr97638.c: New test.a
next prev parent reply other threads:[~2020-11-02 15:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-30 11:16 [Bug target/97638] New: " nsz at gcc dot gnu.org 2020-11-02 15:53 ` cvs-commit at gcc dot gnu.org [this message] 2020-11-09 14:51 ` [Bug target/97638] " cvs-commit at gcc dot gnu.org 2021-02-08 13:17 ` wilco 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-97638-4-cZEvCRlvsI@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).