honorable-parrot/linux-wasm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #1 from davidmalcolm/patch-1

Browse Source 
Fix typo: "Harward" -> "Harvard"
This commit is contained in:
Joel Severin 2025-11-03 12:36:00 +01:00 committed by GitHub
commit 1fcf35d43f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
runtime/index.html
View File

@ -155,7 +155,7 @@ Examples: ls watch uptime head /proc/cpuinfo
<h2>What are the limitations?</h2> <h2>What are the limitations?</h2>
<p> <p>
As mentioned above, no interruptions of tasks are possible. No MMU, every process and the kernel lives in the same As mentioned above, no interruptions of tasks are possible. No MMU, every process and the kernel lives in the same
address space. Wasm is a more or less a strict Harward architecture, where code can be loaded but not modified at address space. Wasm is a more or less a strict Harvard architecture, where code can be loaded but not modified at
runtime. JIT compilation could in theory still work, you would just need to compile the code before launching it, runtime. JIT compilation could in theory still work, you would just need to compile the code before launching it,
but no runtime patching would be allowed (for example, the <i>jump label</i> kernel feature would not work well). but no runtime patching would be allowed (for example, the <i>jump label</i> kernel feature would not work well).
</p> </p>
@ -260,4 +260,4 @@ Examples: ls watch uptime head /proc/cpuinfo
clone-based vforks, unlike in traditional vforks where the double-return on the same stack forbids this). clone-based vforks, unlike in traditional vforks where the double-return on the same stack forbids this).
</p> </p>
</article> </article>
</body> </body>