From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: Commit: GAS: MSP430: Change -mz command line option to -my
Date: Tue, 03 Jun 2014 07:48:00 -0000 [thread overview]
Message-ID: <87r4361lic.fsf@redhat.com> (raw)
Hi Guys,
I am applying the patch below to change the -mz and -mZ command line
options of the MSP430 port of GAS into -my and -mY respectively. This
is because -mz is already in use by the generic part of gas and so was
never received by the msp430 backend.
Cheers
Nick
gas/ChangeLog
2014-06-03 Nick Clifton <nickc@redhat.com>
* config/tc-msp430.c (OPTION_WARN_INTR_NOPS): Use y instead of z.
(OPTION_NO_WARN_INTR_NOPS): Use Y instead of Z.
* doc/c-msp430.texi: Update command line option description.
gas/testsuite/ChangeLog
2014-06-03 Nick Clifton <nickc@redhat.com>
* gas/msp430/bad.d: Use -my not -mz.
diff --git a/gas/config/tc-msp430.c b/gas/config/tc-msp430.c
index 2db0fc0..1398b8c 100644
--- a/gas/config/tc-msp430.c
+++ b/gas/config/tc-msp430.c
@@ -673,8 +673,8 @@ static bfd_boolean large_model = FALSE;
#define OPTION_NO_INTR_NOPS 'N'
#define OPTION_INTR_NOPS 'n'
static bfd_boolean gen_interrupt_nops = FALSE;
-#define OPTION_WARN_INTR_NOPS 'z'
-#define OPTION_NO_WARN_INTR_NOPS 'Z'
+#define OPTION_WARN_INTR_NOPS 'y'
+#define OPTION_NO_WARN_INTR_NOPS 'Y'
static bfd_boolean warn_interrupt_nops = TRUE;
#define OPTION_MCPU 'c'
#define OPTION_MOVE_DATA 'd'
@@ -919,7 +919,7 @@ const pseudo_typeS md_pseudo_table[] =
{NULL, NULL, 0}
};
-const char *md_shortopts = "mm:,mP,mQ,ml,mN,mn,mz,mZ";
+const char *md_shortopts = "mm:,mP,mQ,ml,mN,mn,my,mY";
struct option md_longopts[] =
{
@@ -930,8 +930,8 @@ struct option md_longopts[] =
{"ml", no_argument, NULL, OPTION_LARGE},
{"mN", no_argument, NULL, OPTION_NO_INTR_NOPS},
{"mn", no_argument, NULL, OPTION_INTR_NOPS},
- {"mZ", no_argument, NULL, OPTION_NO_WARN_INTR_NOPS},
- {"mz", no_argument, NULL, OPTION_WARN_INTR_NOPS},
+ {"mY", no_argument, NULL, OPTION_NO_WARN_INTR_NOPS},
+ {"my", no_argument, NULL, OPTION_WARN_INTR_NOPS},
{"md", no_argument, NULL, OPTION_MOVE_DATA},
{NULL, no_argument, NULL, 0}
};
@@ -955,9 +955,9 @@ md_show_usage (FILE * stream)
fprintf (stream,
_(" -mn - insert a NOP after changing interrupts\n"));
fprintf (stream,
- _(" -mZ - do not warn about missing NOPs after changing interrupts\n"));
+ _(" -mY - do not warn about missing NOPs after changing interrupts\n"));
fprintf (stream,
- _(" -mz - warn about missing NOPs after changing interrupts (default)\n"));
+ _(" -my - warn about missing NOPs after changing interrupts (default)\n"));
fprintf (stream,
_(" -md - Force copying of data from ROM to RAM at startup\n"));
}
diff --git a/gas/doc/c-msp430.texi b/gas/doc/c-msp430.texi
index c539946..cae3d8a 100644
--- a/gas/doc/c-msp430.texi
+++ b/gas/doc/c-msp430.texi
@@ -61,7 +61,7 @@ disables the generation of a NOP instruction following any instruction
that might change the interrupts enabled/disabled state. This is the
default behaviour.
-@item -mz
+@item -my
tells the assembler to generate a warning message if a NOP does not
immediately forllow an instruction that enables or disables
interrupts. This is the default.
@@ -70,7 +70,7 @@ Note that this option can be stacked with the @option{-mn} option so
that the assembler will both warn about missing NOP instructions and
then insert them automatically.
-@item -mZ
+@item -mY
disables warnings about missing NOP instructions.
@item -md
diff --git a/gas/testsuite/gas/msp430/bad.d b/gas/testsuite/gas/msp430/bad.d
index 1a067b5..749759e 100644
--- a/gas/testsuite/gas/msp430/bad.d
+++ b/gas/testsuite/gas/msp430/bad.d
@@ -1,4 +1,4 @@
#name: Diagnostics Quality
#source: bad.s
-#as: -mz
+#as: -my
#error-output: bad.l
reply other threads:[~2014-06-03 7:48 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=87r4361lic.fsf@redhat.com \
--to=nickc@redhat.com \
--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).