cdo/wipforth
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: cdo/wipforth:804626ddad6e4374bc0512ee7b31e4248f5b70a9
Branches Tags
cdo/wipforth:main cdo/wipforth:profiler
...
compare: cdo/wipforth:58e2cf3e1f3729883f623987cf3e0ae7a33a704b
Branches Tags
cdo/wipforth:main cdo/wipforth:profiler

2 Commits
804626ddad ... 58e2cf3e1f

Author SHA1 Message Date
cdo 58e2cf3e1f Fix SharedArrayBuffer name in README 2026-03-20 13:36:54 +00:00
cdo efdae93d90 Add favicon to deploy manifest 2026-03-20 13:35:59 +00:00
2 changed files with 2 additions and 1 deletions
Expand all files Collapse all files
README.md
+1 -1
View File
@@ -29,7 +29,7 @@ and use the system from there.
However, since everything is bootstrapped on the client, basically any However, since everything is bootstrapped on the client, basically any
HTTP server will do as long as it sets the appropriate response HTTP server will do as long as it sets the appropriate response
headers for `SharedMemoryBuffer` use: headers for `SharedArrayBuffer` use:
- `Cross-Origin-Opener-Policy: same-origin` - `Cross-Origin-Opener-Policy: same-origin`
- `Cross-Origin-Embedder-Policy: require-corp` - `Cross-Origin-Embedder-Policy: require-corp`
deploy-manifest.conf
+1
View File
@@ -1,6 +1,7 @@
asm.js asm.js
boot.js boot.js
emu.js emu.js
favicon.png
index.html index.html
prelude.f prelude.f
styles.css styles.css