From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Cc: bug-guile@gnu.org
Subject: ref manual errors in assembler insn descriptions
Date: Sat, 11 Mar 2023 08:54:15 -0800 [thread overview]
Message-ID: <8cd017d3-65ee-f59d-0f73-e62b4b48b05a@gmail.com> (raw)
Hi All,
I'm pretty sure the instruction desciprtions shown below in the manual
are in error. Please let me know if my corrections are correct.
Matt
--- vm.texi-orig 2023-03-11 08:40:59.000388237 -0800
+++ vm.texi 2023-03-11 08:48:57.940061512 -0800
@@ -1468,8 +1468,8 @@
@var{obj}, and store it to @var{dst}.
@end deftypefn
-@deftypefn Instruction {} scm-set! s8:@var{dst} s8:@var{idx} s8:@var{obj}
-@deftypefnx Instruction {} scm-set!/immediate s8:@var{dst} c8:@var{idx}
s8:@var{obj}
+@deftypefn Instruction {} scm-set! s8:@var{obj} s8:@var{idx} s8:@var{val}
+@deftypefnx Instruction {} scm-set!/immediate s8:@var{obj} c8:@var{idx}
s8:@var{val}
Store the @code{scm} local @var{val} into object @var{obj} at word
offset @var{idx}.
@end deftypefn
@@ -1490,8 +1490,8 @@
the @code{u64} local @var{dst}.
@end deftypefn
-@deftypefn Instruction {} word-set! s8:@var{dst} s8:@var{idx} s8:@var{obj}
-@deftypefnx Instruction {} word-set!/immediate s8:@var{dst}
c8:@var{idx} s8:@var{obj}
+@deftypefn Instruction {} word-set! s8:@var{obj} s8:@var{idx} s8:@var{val}
+@deftypefnx Instruction {} word-set!/immediate s8:@var{obj}
c8:@var{idx} s8:@var{val}
Store the @code{u64} local @var{val} into object @var{obj} at word
offset @var{idx}.
@end deftypefn
@@ -1501,7 +1501,7 @@
to the unboxed pointer local @var{dst}.
@end deftypefn
-@deftypefn Instruction {} pointer-set!/immediate s8:@var{dst}
c8:@var{idx} s8:@var{obj}
+@deftypefn Instruction {} pointer-set!/immediate s8:@var{obj}
c8:@var{idx} s8:@var{val}
Store the unboxed pointer local @var{val} into object @var{obj} at word
offset @var{idx}.
@end deftypefn
reply other threads:[~2023-03-11 16:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8cd017d3-65ee-f59d-0f73-e62b4b48b05a@gmail.com \
--to=matt.wette@gmail.com \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.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).