public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97638] New: aarch64: bti c is missing at function entry with branch-protection Date: Fri, 30 Oct 2020 11:16:14 +0000 [thread overview] Message-ID: <bug-97638-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97638 Bug ID: 97638 Summary: aarch64: bti c is missing at function entry with branch-protection Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: nsz at gcc dot gnu.org Target Milestone: --- gcc-10 (and trunk) with -mbranch-protection=bti (or standard) fails to generate bti c at function entry in some cases: char *foo (const char *s, const int c) { const char *p = 0; for (;;) { if (*s == c) p = s; if (p != 0 || *s++ == 0) break; } return (char *)p; } gcc -O2 -mbranch-protection=bti is foo: .L3: ldrb w2, [x0] cmp w2, w1 beq .L2 add x0, x0, 1 cbnz w2, .L3 mov x0, 0 .L2: ret
next reply other threads:[~2020-10-30 11:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-30 11:16 nsz at gcc dot gnu.org [this message] 2020-11-02 15:53 ` [Bug target/97638] " cvs-commit at gcc dot gnu.org 2020-11-09 14:51 ` 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@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).