public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106721] Error: invalid character '<' in mnemonic since r13-2122-g86c0d98620ee3a
Date: Wed, 24 Aug 2022 01:12:05 +0000 [thread overview]
Message-ID: <bug-106721-4-jGL13MN7dN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106721-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106721
--- Comment #4 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 53494 [details]
> gcc13-pr106721.patch
>
> Untested fix. This fixes all <[a-zA-Z] occurrences in tmp-mddump.md (except
> those in comments). Whether for V*BF or V*HF modes it is better to use i or
> f suffixed broadcast etc. is something I have no idea about, used f for now.
Maybe we should align them with V*HImode like other vector shuffle, broadcast
instructions, which means use i instead?
Others LGTM, thanks for the fix.
next parent reply other threads:[~2022-08-24 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106721-4@http.gcc.gnu.org/bugzilla/>
2022-08-24 1:12 ` crazylht at gmail dot com [this message]
2022-08-24 8:01 ` cvs-commit at gcc dot gnu.org
2022-08-29 10:06 ` cvs-commit at gcc dot gnu.org
2022-08-30 9:11 ` jakub at gcc dot gnu.org
2022-11-04 8:30 ` cvs-commit at gcc dot gnu.org
2022-11-28 22:12 ` pinskia at gcc dot gnu.org
2023-03-20 5:31 ` 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-106721-4-jGL13MN7dN@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).