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/99988] aarch64: GCC generates excessive consecutive bti j instructions Date: Thu, 22 Apr 2021 12:46:34 +0000 [thread overview] Message-ID: <bug-99988-4-yLZUBkJJvZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99988-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99988 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>: https://gcc.gnu.org/g:d44d8ed6b4e6fb2d0cf7566214e2e8281dd44cf0 commit r12-58-gd44d8ed6b4e6fb2d0cf7566214e2e8281dd44cf0 Author: Christophe Lyon <christophe.lyon@linaro.org> Date: Thu Apr 22 12:43:25 2021 +0000 testsuite/aarch64: Run pr99988.c test under lp64 only The new test fails with -mabi=ilp32: sorry, unimplemented: return address signing is only supported for '-mabi=lp64' 2021-04-22 Christophe Lyon <christophe.lyon@linaro.org> gcc/testsuite/ PR target/99988 * gcc.target/aarch64/pr99988.c: Skip if not lp64 target.
next prev parent reply other threads:[~2021-04-22 12:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-09 10:13 [Bug target/99988] New: " acoplan at gcc dot gnu.org 2021-04-09 10:23 ` [Bug target/99988] " acoplan at gcc dot gnu.org 2021-04-09 11:29 ` acoplan at gcc dot gnu.org 2021-04-21 13:42 ` cvs-commit at gcc dot gnu.org 2021-04-21 13:46 ` acoplan at gcc dot gnu.org 2021-04-22 12:46 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-11 15:15 ` cvs-commit at gcc dot gnu.org 2021-05-12 9:58 ` cvs-commit at gcc dot gnu.org 2021-05-12 15:03 ` cvs-commit at gcc dot gnu.org 2021-05-12 15:08 ` acoplan 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-99988-4-yLZUBkJJvZ@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).