public inbox for binutils-cvs@sourceware.org help / color / mirror / Atom feed
From: Claudiu Zissulescu <claziss@sourceware.org> To: bfd-cvs@sourceware.org Subject: [binutils-gdb] arc: Update missing cipher. Date: Mon, 18 Jul 2022 11:25:42 +0000 (GMT) [thread overview] Message-ID: <20220718112542.2A3493853564@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5154216259b0302785abf89f176051bcf0e6375c commit 5154216259b0302785abf89f176051bcf0e6375c Author: Claudiu Zissulescu <claziss@synopsys.com> Date: Mon Jul 18 13:57:10 2022 +0300 arc: Update missing cipher. The ciphers 5,7, and 9 are missing when parsing an assembly instruction leading to errors when those ciphers are used. gas/config * tc-arc.c (md_assembly): Update strspn string with the missing ciphers. Signed-off-by: Claudiu Zissulescu <claziss@synopsys.com> Diff: --- gas/ChangeLog | 5 +++++ gas/config/tc-arc.c | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/gas/ChangeLog b/gas/ChangeLog index 4c2b03ef216..5a391a22636 100644 --- a/gas/ChangeLog +++ b/gas/ChangeLog @@ -1,3 +1,8 @@ +2022-07-18 Claudiu Zissulescu <claziss@synopsys.com> + + * config/tc-arc.c (md_assembly): Update strspn string with the + missing ciphers. + 2022-07-08 Nick Clifton <nickc@redhat.com> * 2.39 branch created. diff --git a/gas/config/tc-arc.c b/gas/config/tc-arc.c index fd648b742b4..a606078f5b8 100644 --- a/gas/config/tc-arc.c +++ b/gas/config/tc-arc.c @@ -2517,7 +2517,7 @@ md_assemble (char *str) struct arc_flags flags[MAX_INSN_FLGS]; /* Split off the opcode. */ - opnamelen = strspn (str, "abcdefghijklmnopqrstuvwxyz_0123468"); + opnamelen = strspn (str, "abcdefghijklmnopqrstuvwxyz_0123456789"); opname = xmemdup0 (str, opnamelen); /* Signalize we are assembling the instructions. */
reply other threads:[~2022-07-18 11:25 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220718112542.2A3493853564@sourceware.org \ --to=claziss@sourceware.org \ --cc=bfd-cvs@sourceware.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).