diff options
| author | Irene Knapp <ireneista@irenes.space> | 2026-05-28 19:34:07 -0700 |
|---|---|---|
| committer | Irene Knapp <ireneista@irenes.space> | 2026-05-28 20:28:48 -0700 |
| commit | 3b00a5376036bb3f50a1a1f97d136305a2d03a57 (patch) | |
| tree | c08ec1927761909aa76981d9eb964725e00ddc72 /linux-dynamic.e | |
| parent | d9a82e9f3c87aa318fb05819249656b43fde15e3 (diff) | |
change the parameter order for memcopy and memmove
that was surprisingly involved, but it feels like the right thing to do Change-Id: Ia2f38c7278f4237cebd0435d27131fe32dbc3718 Force-Push: yes
Diffstat (limited to 'linux-dynamic.e')
| -rw-r--r-- | linux-dynamic.e | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/linux-dynamic.e b/linux-dynamic.e index 4c73bb7..7890043 100644 --- a/linux-dynamic.e +++ b/linux-dynamic.e @@ -97,9 +97,6 @@ ~ It's possible to set up an alternate stack for signal handlers. We don't, ~ though, so it's possible this code has bitrotted. At the very least, it ~ should be more configurable than this. -~ -~ Note that for it to actually be used, there also needs to be a flag set -~ at the time the action is bound. : prepare-signal-stack here @ 2048 packalign here ! 1024 1024 * 4 * allocate @@ -270,7 +267,7 @@ ~ (saved location, second half execution token) ~ Something subtle here: That above "codeword" was actually a word - ~ pointer. See, because we're pretending the wrapper is Forth word, even + ~ pointer. See, because we're pretending the wrapper is a Forth word, even ~ though we're writing it in assembly, so "returning" to it means invoking ~ the next word pointer in the word pointer array that is its compiled form. ~ Instead of creating a separate memory area though, we just put the pointer |