From: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>
To: gdb-patches@sourceware.org, pedro_alves@portugalmail.pt,
ambrogino.modigliani@gmail.com, ambrogino.modigliani@mail.com
Subject: [PATCH 15/17] Fix spelling in comments in .opc files (cpu)
Date: Fri, 25 Nov 2016 19:48:00 -0000 [thread overview]
Message-ID: <1480103203-9710-16-git-send-email-ambrogino.modigliani@mail.com> (raw)
In-Reply-To: <1480103203-9710-1-git-send-email-ambrogino.modigliani@mail.com>
cpu/ChangeLog:
* frv.opc: Fix spelling in comments.
* mep.opc: Fix spelling in comments.
---
cpu/frv.opc | 2 +-
cpu/mep.opc | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/cpu/frv.opc b/cpu/frv.opc
index 869155d..2c23b07 100644
--- a/cpu/frv.opc
+++ b/cpu/frv.opc
@@ -488,7 +488,7 @@ match_vliw (VLIW_COMBO *vliw1, VLIW_COMBO *vliw2, int vliw_size)
return TRUE;
}
-/* Find the next vliw vliw in the table that can accomodate the new insn.
+/* Find the next vliw vliw in the table that can accommodate the new insn.
If one is found then return it. Otherwise return NULL. */
static VLIW_COMBO *
diff --git a/cpu/mep.opc b/cpu/mep.opc
index 7ed3ea8..2b59392 100644
--- a/cpu/mep.opc
+++ b/cpu/mep.opc
@@ -1163,7 +1163,7 @@ mep_examine_vliw32_insns (CGEN_CPU_DESC cd, bfd_vma pc, disassemble_info *info)
cop1buflength = 2;
}
- /* Now we have the distrubution set. Print them out. */
+ /* Now we have the distribution set. Print them out. */
status = mep_print_vliw_insns (cd, pc, info, buf, corebuflength,
cop1buflength, cop2buflength);
@@ -1252,7 +1252,7 @@ mep_examine_vliw64_insns (CGEN_CPU_DESC cd, bfd_vma pc, disassemble_info *info)
cop1buflength = 6;
}
- /* Now we have the distrubution set. Print them out. */
+ /* Now we have the distribution set. Print them out. */
status = mep_print_vliw_insns (cd, pc, info, buf, corebuflength,
cop1buflength, cop2buflength);
--
2.7.4
next prev parent reply other threads:[~2016-11-25 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 19:48 [PATCH 00/17] Fix spelling mistakes in comments - GDB Ambrogino Modigliani
2016-11-25 19:47 ` [PATCH 06/17] Fix spelling in comments in C source files (readline) Ambrogino Modigliani
2016-11-25 20:42 ` Mike Frysinger
2016-11-25 19:47 ` [PATCH 05/17] Fix spelling in comments in C source files (opcodes) Ambrogino Modigliani
2016-11-25 19:47 ` [PATCH 10/17] Fix spelling in comments in .cpu files (cpu) Ambrogino Modigliani
2016-11-25 19:47 ` [PATCH 17/17] Fix spelling in comments in .tbl files (opcodes) Ambrogino Modigliani
2016-11-25 19:47 ` [PATCH 07/17] Fix spelling in comments in Assembler files (gdb) Ambrogino Modigliani
2016-11-25 19:47 ` [PATCH 08/17] Fix spelling in comments in Expect scripts (gdb) Ambrogino Modigliani
2016-11-25 19:47 ` [PATCH 12/17] Fix spelling in comments in .in files (readline) Ambrogino Modigliani
2016-11-25 19:47 ` [PATCH 11/17] Fix spelling in comments in .in files (opcodes) Ambrogino Modigliani
2016-11-25 19:48 ` [PATCH 01/17] Fix spelling in comments in C source files (bfd) Ambrogino Modigliani
2016-11-25 19:48 ` Ambrogino Modigliani [this message]
2016-11-25 19:48 ` [PATCH 16/17] Fix spelling in comments in .opc files (opcodes) Ambrogino Modigliani
2016-11-25 19:48 ` [PATCH 03/17] Fix spelling in comments in C source files (include) Ambrogino Modigliani
2016-11-25 21:15 ` Joseph Myers
2016-11-25 19:48 ` [PATCH 04/17] Fix spelling in comments in C source files (intl) Ambrogino Modigliani
2016-11-25 21:11 ` Joseph Myers
2016-11-25 19:48 ` [PATCH 13/17] Fix spelling in comments in .l files (gdb) Ambrogino Modigliani
2016-11-25 19:48 ` [PATCH 14/17] Fix spelling in comments in .m4 files (config) Ambrogino Modigliani
2016-11-25 19:48 ` [PATCH 02/17] Fix spelling in comments in C source files (gdb) Ambrogino Modigliani
2016-11-25 19:48 ` [PATCH 09/17] Fix spelling in comments in XML " Ambrogino Modigliani
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=1480103203-9710-16-git-send-email-ambrogino.modigliani@mail.com \
--to=ambrogino.modigliani@gmail.com \
--cc=ambrogino.modigliani@mail.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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).