From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: binutils@sourceware.org
Subject: moxie fixes in gas
Date: Wed, 26 Aug 2009 07:14:00 -0000 [thread overview]
Message-ID: <20090826050710.GA8346@gmx.de> (raw)
This allows the build to complete in gas with a moxie target. Without
the patch, 'make' won't know config/tc-moxie.c is a prerequisite to
tc-moxie.o. The makefile bug might have had more benign effects before
the dependency tracking changes, but now they are definitely needed.
The syntax error in the .c file doesn't instill confidence though. :-)
OK to apply?
Thanks,
Ralf
moxie fixes in gas.
gas/ChangeLog:
2009-08-26 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* Makefile.am (TARGET_CPU_CFILES): Add config/tc-moxie.c.
* config/tc-moxie.c (md_assemble): Fix typos in strings. Fix
syntax error.
* Makefile.in: Regenerate.
* po/POTFILES.in: Likewise.
* po/gas.pot: Likewise.
diff --git a/gas/Makefile.am b/gas/Makefile.am
index 27a7d1a..b8e86b1 100644
--- a/gas/Makefile.am
+++ b/gas/Makefile.am
@@ -275,6 +275,7 @@ TARGET_CPU_CFILES = \
config/tc-mmix.c \
config/tc-mn10200.c \
config/tc-mn10300.c \
+ config/tc-moxie.c \
config/tc-msp430.c \
config/tc-mt.c \
config/tc-ns32k.c \
diff --git a/gas/config/tc-moxie.c b/gas/config/tc-moxie.c
index f5140c5..3ec00a7 100644
--- a/gas/config/tc-moxie.c
+++ b/gas/config/tc-moxie.c
@@ -199,7 +199,7 @@ md_assemble (char *str)
reg = parse_register_operand (&op_end);
iword += (reg << 8);
if (*op_end != ',')
- as_warn (_("expecting comma delimeted register operands"));
+ as_warn (_("expecting comma delimited register operands"));
op_end++;
op_end = parse_exp_save_ilp (op_end, &arg);
fix_new_exp (frag_now,
@@ -218,7 +218,7 @@ md_assemble (char *str)
int dest, src;
dest = parse_register_operand (&op_end);
if (*op_end != ',')
- as_warn (_("expecting comma delimeted register operands"0);
+ as_warn (_("expecting comma delimited register operands"));
op_end++;
src = parse_register_operand (&op_end);
iword += (dest << 4) + src;
@@ -309,7 +309,7 @@ md_assemble (char *str)
int a, b;
a = parse_register_operand (&op_end);
if (*op_end != ',')
- as_warn (_("expecting comma delimeted register operands"));
+ as_warn (_("expecting comma delimited register operands"));
op_end++;
if (*op_end != '(')
{
@@ -355,7 +355,7 @@ md_assemble (char *str)
}
op_end++;
if (*op_end != ',')
- as_warn (_("expecting comma delimeted register operands"));
+ as_warn (_("expecting comma delimited register operands"));
op_end++;
b = parse_register_operand (&op_end);
iword += (a << 4) + b;
diff --git a/gas/po/POTFILES.in b/gas/po/POTFILES.in
index 5ca5ea1..1a3a671 100644
--- a/gas/po/POTFILES.in
+++ b/gas/po/POTFILES.in
@@ -105,6 +105,7 @@ config/tc-mn10200.c
config/tc-mn10200.h
config/tc-mn10300.c
config/tc-mn10300.h
+config/tc-moxie.c
config/tc-msp430.c
config/tc-msp430.h
config/tc-mt.c
next reply other threads:[~2009-08-26 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 7:14 Ralf Wildenhues [this message]
2009-08-26 7:20 ` Alan Modra
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=20090826050710.GA8346@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=binutils@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: 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).