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/106721] Error: invalid character '<' in mnemonic since r13-2122-g86c0d98620ee3a Date: Fri, 04 Nov 2022 08:30:59 +0000 [thread overview] Message-ID: <bug-106721-4-lC488Wn7HE@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 #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:edf40e86344c407cadca769a6496905a0ec31e48 commit r11-10358-gedf40e86344c407cadca769a6496905a0ec31e48 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Aug 24 09:57:09 2022 +0200 i386: Fix up mode iterators that weren't expanded [PR106721] Currently, when md file reader sees <something> and something is valid mode (or code) attribute but which doesn't include case for the current mode (or code), it just keeps the <something> untouched. I went through all cases matching <[a-zA-Z] in tmp-mddump.md after make mddump. One of the cases was related to the V*HF mode additions and there was one typo. 2022-08-24 Jakub Jelinek <jakub@redhat.com> PR target/106721 * config/i386/sse.md (avx512er_vmrcp28<mode><mask_name><round_saeonly_name>): Fix typo, mask_opernad3 -> mask_operand3. (cherry picked from commit 846e5c009e360f0c4fe58ff0d3aee03ebe3ca1a9)
next prev parent reply other threads:[~2022-11-04 8:31 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 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 [this message] 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-lC488Wn7HE@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).