public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101723] New: arm: incorrect order of .fpu and .arch_extension directives leads to unsupported instructions Date: Mon, 02 Aug 2021 10:48:17 +0000 [thread overview] Message-ID: <bug-101723-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101723 Bug ID: 101723 Summary: arm: incorrect order of .fpu and .arch_extension directives leads to unsupported instructions Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: rearnsha at gcc dot gnu.org Target Milestone: --- This bug was originally reported against GNU binutils (https://sourceware.org/bugzilla/show_bug.cgi?id=28078), but is really a problem with the way GCC emits the directives .fpu and .arch_extension. Alok Parlikar 2021-07-12 04:50:04 UTC I was trying to build tensorflow-lite v2.5 with a custom toolchain that was using binutils 2.36.1. The build failed when building the xnnpack project with an error: /tmp/ccMSJOfk.s:380: Error: selected processor does not support `vsdot.s8 q12,q9,d11[0]' in ARM mode Some of my notes about this issue are here: https://github.com/google/XNNPACK/issues/1465#issuecomment-877910701 Following is a minimal example to reproduce this: // file: test.c #include <arm_neon.h> int32x2_t test(int32x2_t a, int8x8_t b, int8x8_t c) { return vdot_lane_s32(a, b, c, 1); } // EOF
next reply other threads:[~2021-08-02 10:48 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 10:48 rearnsha at gcc dot gnu.org [this message] 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 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@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).