From: Kautuk Consul <kconsul@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Thomas Huth <thuth@redhat.com>,
aik@ozlabs.ru, groug@kaod.org
Cc: slof@lists.ozlabs.org, kvm-ppc@vger.kernel.org,
Kautuk Consul <kconsul@linux.vnet.ibm.com>
Subject: [PATCH v2] slof/engine.in: refine +COMP and -COMP by not using COMPILE
Date: Fri, 2 Feb 2024 00:15:48 -0500 [thread overview]
Message-ID: <20240202051548.877087-1-kconsul@linux.vnet.ibm.com> (raw)
Use the standard "DOTICK <word> COMPILE," mechanism in +COMP and -COMP
as is being used by the rest of the compiler.
Also use "SEMICOLON" instead of "EXIT" to compile into HERE in -COMP
as that is more informative as it mirrors the way the col() macro defines
a colon definition.
Signed-off-by: Kautuk Consul <kconsul@linux.vnet.ibm.com>
---
slof/engine.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/slof/engine.in b/slof/engine.in
index 59e82f1..fa4d82e 100644
--- a/slof/engine.in
+++ b/slof/engine.in
@@ -422,8 +422,8 @@ imm(.( LIT(')') PARSE TYPE)
col(COMPILE R> CELL+ DUP @ COMPILE, >R)
var(THERE 0)
-col(+COMP STATE @ 1 STATE +! 0BRANCH(1) EXIT HERE THERE ! COMP-BUFFER DOTO HERE COMPILE DOCOL)
-col(-COMP -1 STATE +! STATE @ 0BRANCH(1) EXIT COMPILE EXIT THERE @ DOTO HERE COMP-BUFFER EXECUTE)
+col(+COMP STATE @ 1 STATE +! 0BRANCH(1) EXIT HERE THERE ! COMP-BUFFER DOTO HERE DOTICK DOCOL COMPILE,)
+col(-COMP -1 STATE +! STATE @ 0BRANCH(1) EXIT DOTICK SEMICOLON COMPILE, THERE @ DOTO HERE COMP-BUFFER EXECUTE)
// Structure words.
col(RESOLVE-ORIG HERE OVER CELL+ - SWAP !)
--
2.31.1
next reply other threads:[~2024-02-02 5:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 5:15 Kautuk Consul [this message]
2024-02-12 9:28 ` [PATCH v2] slof/engine.in: refine +COMP and -COMP by not using COMPILE Kautuk Consul
2024-02-23 20:57 ` Segher Boessenkool
2024-02-26 4:39 ` Kautuk Consul
2024-03-07 6:33 ` Kautuk Consul
2024-03-18 5:12 ` Kautuk Consul
2024-05-22 9:04 ` Kautuk Consul
2024-05-27 12:33 ` Alexey Kardashevskiy
2024-05-28 4:02 ` Kautuk Consul
2024-02-22 7:38 ` Kautuk Consul
2024-02-22 9:04 ` Thomas Huth
2024-02-22 11:46 ` Kautuk Consul
2024-02-23 5:59 ` Kautuk Consul
2024-02-23 21:04 ` Segher Boessenkool
2024-02-26 4:32 ` Kautuk Consul
2024-02-26 4:43 ` Kautuk Consul
2024-02-26 6:47 ` Kautuk Consul
2024-02-26 6:59 ` Kautuk Consul
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=20240202051548.877087-1-kconsul@linux.vnet.ibm.com \
--to=kconsul@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=groug@kaod.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=segher@kernel.crashing.org \
--cc=slof@lists.ozlabs.org \
--cc=thuth@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).