public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stammark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107714] MVE: Invalid addressing mode generated for VLD2
Date: Thu, 17 Nov 2022 16:43:20 +0000 [thread overview]
Message-ID: <bug-107714-4-2SWfeLMBfQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107714-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714
Stam Markianos-Wright <stammark at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-11-17
--- Comment #3 from Stam Markianos-Wright <stammark at gcc dot gnu.org> ---
Thanks for finding this! Confirmed the `vld2` bug on latest trunk -- my guess
would be either a GCC backend or a gas bug (I'm not familiar with these
instructions).
For the `vmulq` issue I'll reply under the other thread, but I believe that
very soon we'll be able to put that down as "already fixed", so we can keep
this thread for `vld2` only.
next prev parent reply other threads:[~2022-11-17 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 12:56 [Bug target/107714] New: " kevin.bracey at alifsemi dot com
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 [this message]
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-2SWfeLMBfQ@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: link
Be 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).