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/101723] arm: incorrect order of .fpu and .arch_extension directives leads to unsupported instructions Date: Wed, 18 Aug 2021 15:23:30 +0000 [thread overview] Message-ID: <bug-101723-4-82SmtEkf0Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101723-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101723 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Earnshaw <rearnsha@gcc.gnu.org>: https://gcc.gnu.org/g:b8a001599d21eaa77737df7efc6bc206e6964cdf commit r11-8883-gb8a001599d21eaa77737df7efc6bc206e6964cdf Author: Christophe Lyon <christophe.lyon@foss.st.com> Date: Fri Aug 6 14:25:47 2021 +0000 arm: Fix pr69245.c testcase for reorder assembler architecture directives [PR101723] In gcc.target/arm/pr69245.c, to have a .fpu neon-vfpv4 directive, make sure code for fn1() is emitted, by removing the static keyword. Fix a typo in gcc.target/arm/pr69245.c, where \s should be \\s. 2021-08-06 Christophe Lyon <christophe.lyon@foss.st.com> gcc/testsuite/ PR target/101723 * gcc.target/arm/pr69245.c: Make sure to emit code for fn1, fix typo. (cherry picked from commit aff75af3b50f8c039ed6fbfa3f313ba45d44f6e6)
next prev parent reply other threads:[~2021-08-18 15:23 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 10:48 [Bug target/101723] New: " rearnsha at gcc dot gnu.org 2021-08-02 10:48 ` [Bug target/101723] " rearnsha at gcc dot gnu.org 2021-08-02 10:50 ` rearnsha at gcc dot gnu.org 2021-08-05 11:52 ` cvs-commit at gcc dot gnu.org 2021-08-06 14:07 ` cvs-commit at gcc dot gnu.org 2021-08-06 14:27 ` cvs-commit at gcc dot gnu.org 2021-08-18 15:23 ` cvs-commit at gcc dot gnu.org 2021-08-18 15:23 ` cvs-commit at gcc dot gnu.org 2021-08-18 15:23 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-23 14:31 ` cvs-commit at gcc dot gnu.org 2021-08-23 14:32 ` cvs-commit at gcc dot gnu.org 2021-08-23 14:32 ` cvs-commit at gcc dot gnu.org 2021-08-23 14:41 ` cvs-commit at gcc dot gnu.org 2021-08-23 14:41 ` cvs-commit at gcc dot gnu.org 2021-08-23 14:43 ` rearnsha at gcc dot gnu.org 2021-08-26 15:18 ` clyon at gcc dot gnu.org 2021-08-31 11:25 ` rearnsha at gcc dot gnu.org 2021-09-01 8:14 ` clyon at gcc dot gnu.org 2022-02-08 7:12 ` pinskia 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-101723-4-82SmtEkf0Z@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).