From 8d9d687783b06e87e2b940e0c498a7f2b8c9846f Mon Sep 17 00:00:00 2001 From: "Jose E. Marchesi" Date: Tue, 14 May 2019 20:32:40 +0200 Subject: [PATCH] manual: remove obsolete comment about using multi-ifields in operands 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 * 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 + + * doc/rtl.texi (Instruction operands): Remove obsolete comment + about multi-ifields. + 2019-01-01 Alan Modra * 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.43.5