public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: cgen@sourceware.org
Subject: [PATCH 1/1] manual: remove obsolete comment about using multi-ifields in operands
Date: Tue, 14 May 2019 18:32:00 -0000	[thread overview]
Message-ID: <20190514183240.11769-1-jose.marchesi@oracle.com> (raw)

This little patch removes an obsolete comment from the manual.
Multi-ifields certainly work as indexes in instruction operands.

Salud!

ChangeLog:

2019-05-14  Jose E. Marchesi  <jose.marchesi@oracle.com>

	* doc/rtl.texi (Instruction operands): Remove obsolete comment
	about multi-ifields.
---
 ChangeLog    | 5 +++++
 doc/rtl.texi | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index 9add333..bd13933 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2019-05-14  Jose E. Marchesi  <jose.marchesi@oracle.com>
+
+	* doc/rtl.texi (Instruction operands): Remove obsolete comment
+	about multi-ifields.
+
 2019-01-01  Alan Modra  <amodra@gmail.com>
 
 	* utils.scm: Update emitted copyright dates.
diff --git a/doc/rtl.texi b/doc/rtl.texi
index 9b41c6d..49d00e3 100644
--- a/doc/rtl.texi
+++ b/doc/rtl.texi
@@ -2027,7 +2027,7 @@ The mode the value is to be interpreted in.
 The index of the hardware element. This is used to mate the hardware
 element with the instruction field that selects it, and must be the name
 of an ifield entry. (*Note: The index may be other things besides
-ifields in the future.)  It must not be a multi-ifield, currently.
+ifields in the future.)
 
 @subsection handlers
 Sometimes it's necessary to escape to C to parse assembler, or print
-- 
2.11.0

             reply	other threads:[~2019-05-14 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 18:32 Jose E. Marchesi [this message]
2019-05-14 18:37 ` Frank Ch. Eigler
2019-05-14 18:52   ` Jose E. Marchesi

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=20190514183240.11769-1-jose.marchesi@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=cgen@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).