public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kevin.bracey at alifsemi dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107714] New: MVE: Invalid addressing mode generated for VLD2 Date: Wed, 16 Nov 2022 12:56:04 +0000 [thread overview] Message-ID: <bug-107714-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 Bug ID: 107714 Summary: MVE: Invalid addressing mode generated for VLD2 Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: kevin.bracey at alifsemi dot com Target Milestone: --- Created attachment 53909 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53909&action=edit Stripped-down reproducer source While I was working on some Helium intrinsics, GCC produced some invalid code, meaning my optimisation can only be enabled in our armclang builds. Problem seems to be still present on GCC trunk. Posted at https://godbolt.org/z/h3EhMvxao Compilation options -O2 -mcpu=cortex-m55 -mfloat-abi=hard Error: instruction does not accept this addressing mode -- `vld21.8 {q4,q5},[r3],r2' Compiler Explorer output for trunk shows the same invalid addressing mode. (It also shows non-existent registers q8 and up in use - I don't know why. Not a problem in my local GCC, obtained from Arm's embedded distribution).
next reply other threads:[~2022-11-16 12:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 12:56 kevin.bracey at alifsemi dot com [this message] 2022-11-16 15:52 ` [Bug target/107714] " kevin.bracey at alifsemi dot com 2022-11-16 16:00 ` kevin.bracey at alifsemi dot com 2022-11-17 16:43 ` stammark at gcc dot gnu.org 2022-11-21 12:12 ` kevin.bracey at alifsemi dot com 2022-11-21 12:49 ` kevin.bracey at alifsemi dot com 2022-12-09 13:29 ` stammark at gcc dot gnu.org 2022-12-30 11:25 ` cvs-commit at gcc dot gnu.org 2023-01-10 13:38 ` cvs-commit at gcc dot gnu.org 2023-01-10 13:41 ` cvs-commit at gcc dot gnu.org 2023-01-16 13:22 ` stammark 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-107714-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).