[nasm:master] doc: move instruction list to the end

[nasm-bot for H. Peter Anvin]

Commit-ID:  7727fbb59a11dd23813fa2469e1f3efd1eaf91da
Gitweb:     http://repo.or.cz/w/nasm.git?a=commitdiff;h=7727fbb59a11dd23813fa2469e1f3efd1eaf91da
Author:     H. Peter Anvin <hpa at zytor.com>
AuthorDate: Tue, 8 Nov 2022 18:40:11 -0800
Committer:  H. Peter Anvin <hpa at zytor.com>
CommitDate: Tue, 8 Nov 2022 18:40:11 -0800

doc: move instruction list to the end

The web site currently assumes that the release history is always in
appendix C. Humor it for now, besides, it doesn't really make sense
for the huge machine-generated instruction list to be anywhere but the
end.

Signed-off-by: H. Peter Anvin <hpa at zytor.com>


---
 doc/nasmdoc.src | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index ddab7c05..f2756072 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -8791,17 +8791,6 @@ data section which wouldn't contain anything you wanted to see
 anyway.
 
 
-\A{inslist} \i{Instruction List}
-
-\H{inslistintro} Introduction
-
-The following sections show the instructions which NASM currently supports. For each
-instruction, there is a separate entry for each supported addressing mode. The third
-column shows the processor type in which the instruction was introduced and,
- when appropriate, one or more usage flags.
-
-\& inslist.src
-
 \A{changelog} \i{NASM Version History}
 
 \& changes.src
@@ -8968,3 +8957,14 @@ for example, the problem involves NASM failing to generate an object
 file while TASM can generate an equivalent file without trouble,
 then send us \e{both} object files, so we can see what TASM is doing
 differently from us.
+
+\A{inslist} \i{Instruction List}
+
+\H{inslistintro} Introduction
+
+The following sections show the instructions which NASM currently supports. For each
+instruction, there is a separate entry for each supported addressing mode. The third
+column shows the processor type in which the instruction was introduced and,
+ when appropriate, one or more usage flags.
+
+\& inslist.src