From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Subject: PATCH: Enable ia64 texinfo
Date: Wed, 09 Feb 2005 09:25:00 -0000 [thread overview]
Message-ID: <20050209011850.GA14937@lucon.org> (raw)
It turned out that ia64 texinfo is never used. This patch fixes it.
H.J.
----
2005-02-08 H.J. Lu <hongjiu.lu@intel.com>
* doc/all.texi: Add IA64.
* doc/as.texinfo: Likewise.
* doc/c-ia64.texi: Fix typoes.
--- gas/doc/all.texi.ia64 2003-04-01 14:29:08.000000000 -0800
+++ gas/doc/all.texi 2005-02-08 16:55:44.381312059 -0800
@@ -40,6 +40,7 @@
@set I80386
@set I860
@set I960
+@set IA64
@set IP2K
@set M32R
@set M68HC11
--- gas/doc/as.texinfo.ia64 2004-11-23 09:09:23.000000000 -0800
+++ gas/doc/as.texinfo 2005-02-08 17:09:37.983569900 -0800
@@ -6039,6 +6039,9 @@ subject, see the hardware manufacturer's
@ifset I960
* i960-Dependent:: Intel 80960 Dependent Features
@end ifset
+@ifset IA64
+* IA-64-Dependent:: Intel IA-64 Dependent Features
+@end ifset
@ifset IP2K
* IP2K-Dependent:: IP2K Dependent Features
@end ifset
--- gas/doc/c-ia64.texi.ia64 2003-10-27 11:00:37.000000000 -0800
+++ gas/doc/c-ia64.texi 2005-02-08 16:58:47.735613721 -0800
@@ -90,7 +90,7 @@ Reference Guide.
* IA-64-Chars:: Special Characters
* IA-64-Regs:: Register Names
* IA-64-Bits:: Bit Names
-* IA-64-Relocs:: Relocations
+@c * IA-64-Relocs:: Relocations // to be written
@end menu
@node IA-64-Chars
@@ -136,7 +136,7 @@ the end-of-interrupt register (@samp{cr6
The assembler defines bit masks for each of the bits in the IA-64
processor status register. For example, @samp{psr.ic} corresponds to
a value of 0x2000. These masks are primarily intended for use with
-the @sample{ssm}/@sample{sum} and @sample{rsm}/@sample{rum}
+the @samp{ssm}/@samp{sum} and @samp{rsm}/@samp{rum}
instructions, but they can be used anywhere else where an integer
constant is expected.
next reply other threads:[~2005-02-09 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 9:25 H. J. Lu [this message]
2005-02-11 9:16 ` James E Wilson
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=20050209011850.GA14937@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).