about summary refs log tree commit diff
path: root/execution.e
diff options
context:
space:
mode:
Diffstat (limited to 'execution.e')
-rw-r--r--execution.e13
1 files changed, 5 insertions, 8 deletions
diff --git a/execution.e b/execution.e
index 8962578..81ec03b 100644
--- a/execution.e
+++ b/execution.e
@@ -418,7 +418,7 @@
 ~ pointers. It was directly jumped to from cold-start. There's nowhere to
 ~ return to, so it needs to never return.
 ~
-~ (output buffer start, output point, input string pointer, delimiter pointer
+~ (output buffer start, output point, input string pointer
 ~  -- output buffer start, output point)
 : output-warm-start
   ~ : blank-line
@@ -452,11 +452,10 @@
   ~   While it's not actually a requirement that codeword pointers be
   ~ word-aligned, it's highly likely that it helps performance. (Whether it
   ~ does is up to Intel's microcode.)
-  4 unroll 3unroll
+  3unroll
   8 packalign
   current-offset L!' warm-start
-  ~ (delimiter pointer, input string pointer,
-  ~  output buffer start, output point)
+  ~ (input string pointer, output buffer start, output point)
 
   ~   Before handing off to us, cold-start pushed a single value onto the
   ~ stack, a pointer to the beginning of the log. Now, we load our entire
@@ -553,10 +552,8 @@
   ~ we can go ahead and dispatch to the log-load transform, and do the rest of
   ~ the code through that.
 
-  ~ (delimiter pointer, input string pointer,
-  ~  output buffer start, output point)
-  3roll 4 roll
-  log-load-transform
+  ~ (input string pointer, output buffer start, output point)
+  3roll log-load-transform
   ~ (output buffer start, output point)
 
   ~ : blank-line