public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia 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: Mon, 20 Mar 2023 05:31:23 +0000 [thread overview] Message-ID: <bug-106721-4-5CbCpuuLJI@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |n.deshmukh at samsung dot com --- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> --- *** Bug 109204 has been marked as a duplicate of this bug. ***
prev parent reply other threads:[~2023-03-20 5: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 2022-11-28 22:12 ` pinskia at gcc dot gnu.org 2023-03-20 5:31 ` pinskia at gcc dot gnu.org [this message]
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-5CbCpuuLJI@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).