From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: <gdb-patches@sources.redhat.com>
Subject: [patch/doc] Replace "M32R/D" with "M32R"
Date: Thu, 23 Oct 2003 00:45:00 -0000 [thread overview]
Message-ID: <00a701c398ff$16a5e880$5169910a@KEI> (raw)
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Hello,
In gdb.texinfo, m32r architecture is called as "M32R/D". But
it is not a proper name for the architecture . Because "D"
means DRAM and "M32R/D" means m32r processors with internal
DRAM. But there are also variations of m32r processors like,
m32r with SRAM, m32r with flash, m32r without internal memory,
and so on.
The attached patch replaces "M32R/D" with "M32R" in gdb.texinfo.
It does not replace "M32R/D" in "Contributor to GDB" because
at that time there was only m32r with DRAM.
OK to commit?
Kei Sakamoto
Renesas Technology Corp.
===
2003-10-23 Kei Sakamoto <sakamoto.kei@renesas.com>
* gdb.texinfo : Replace "M32R/D" with "M32R".
[-- Attachment #2: diffs --]
[-- Type: application/octet-stream, Size: 1008 bytes --]
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.183
diff -u -r1.183 gdb.texinfo
--- gdb.texinfo 23 Oct 2003 00:11:59 -0000 1.183
+++ gdb.texinfo 23 Oct 2003 00:38:12 -0000
@@ -11838,7 +11838,7 @@
* ARM:: ARM
* H8/300:: Renesas H8/300
* H8/500:: Renesas H8/500
-* M32R/D:: Renesas M32R/D
+* M32R:: Renesas M32R
* M68K:: Motorola M68K
* MIPS Embedded:: MIPS Embedded
* OpenRISC 1000:: OpenRisc 1000
@@ -12091,14 +12091,14 @@
@end table
-@node M32R/D
-@subsection Renesas M32R/D
+@node M32R
+@subsection Renesas M32R
@table @code
@kindex target m32r
@item target m32r @var{dev}
-Renesas M32R/D ROM monitor.
+Renesas M32R ROM monitor.
@kindex target m32rsdi
@item target m32rsdi @var{dev}
next reply other threads:[~2003-10-23 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 0:45 Kei Sakamoto [this message]
2003-10-23 5:56 ` Eli Zaretskii
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='00a701c398ff$16a5e880$5169910a@KEI' \
--to=sakamoto.kei@renesas.com \
--cc=gdb-patches@sources.redhat.com \
/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