You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f10baea
Browse filesBrowse the repository at this point in the historyBrowse files
0.29.1: openkal-uefi 0.11.1 and openkal-dos 0.1.1, the DOS row's 1 MiB stack, ovmf 9.2.4-4, dirun 0.6.0 and freebsd-disk-image 14.5-1, mcpp.plugins 0.22.1 (#34)
* 0.29.1: openkal-uefi 0.11.1 and openkal-dos 0.1.1, the DOS row's 1 MiB stack, ovmf 9.2.4-4 and dirun 0.6.0, mcpp.plugins 0.22.0
* mcpp.plugins 0.22.1, whose mcpplibs.os accepts openkal 0.25
* FreeBSD runners: the disk images 14.5-1, whose profile runs the command where a run's files are
Copy file name to clipboardExpand all lines: README.md
+22-11Lines changed: 22 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,24 +165,28 @@ builds openkal-run's core runner as a program of the DOS row below, with the
165
165
image in its `.oke` section. Measured under DOSBox Staging: the image sorted its
166
166
arguments, caught its exception, read DOS's `PATH` and returned 7.
167
167
168
-
Platform 0.29.0 requires mcpp 2026.11.16.1. Every runner here that boots a
168
+
Platform 0.29.0 and 0.29.1 require mcpp 2026.11.16.1. Every runner here that boots a
169
169
machine is enabled on request: the UEFI row's (QEMU and OVMF), the DOS row's
170
170
(DOSBox Staging), and, new, the hosted rows' runners on another system. FreeBSD
171
-
programs run in the FreeBSD virtual machine of xim's disk image packages, and
171
+
programs run in the FreeBSD virtual machine of xim's disk image packages (0.29.1:
172
+
`freebsd-disk-image` 14.5-1, whose profile runs the command in the directory of
173
+
the files a run delivers, `mcpp run --file`), and
172
174
an `x86_64-windows-musl` program runs through Wine on an x86_64 Linux machine.
173
175
Each fetches a machine image or an emulator, or makes a prefix in the home
174
176
directory, on its first use, so `mcpp run` names the runner and how to enable it
175
177
until a project or this machine does:
176
178
177
179
```toml
178
180
[target.x86_64-freebsd-musl]
179
-
platform = "openkal-platform@0.29.0"
181
+
platform = "openkal-platform@0.29.1"
180
182
runner = { enabled = true }
181
183
```
182
184
183
-
The UEFI runner passes the program's arguments (`--`, with ovmf 9.2.4-3's Shell
184
-
profile, whose arguments dirun 0.5.0 quotes for the Shell, so one with a blank
185
-
arrives whole), and openkal-uefi 0.11.0 implements `openkal.fs` over the firmware's
185
+
The UEFI runner passes the program's arguments (`--`, with ovmf 9.2.4-4's Shell
186
+
profile, whose arguments dirun quotes for the Shell, so one with a blank arrives
187
+
whole; openkal-uefi 0.11.1 divides them from the load options, so runs of blanks
188
+
inside one are kept). The application's disk is a writable FAT32 image (dirun
189
+
0.6.0, `disk = "fat-image"`), so it can write files; openkal-uefi implements `openkal.fs` over the firmware's
186
190
file system and `openkal.random` over its RNG protocol, beneath openkal-musl
187
191
0.29.8. okrun is a host for `macos-x86_64` (the release build of openkal-macos
188
192
0.23.4 links) and `linux-i686` (built as `i686-linux-musl`), so `--systems all`
@@ -286,7 +290,7 @@ with `import std`:
286
290
287
291
```toml
288
292
[target.x86_64-uefi]
289
-
platform = "openkal-platform@0.29.0"
293
+
platform = "openkal-platform@0.29.1"
290
294
runner = { enabled = true }
291
295
```
292
296
@@ -321,7 +325,7 @@ run-time over openkal-dos, so it is written in C++23 with `import std`:
321
325
322
326
```toml
323
327
[target.i686-dos-musl]
324
-
platform = "openkal-platform@0.28.0"
328
+
platform = "openkal-platform@0.29.1"
325
329
```
326
330
327
331
The row is TECHNICAL EXPERIMENT ONLY (openkal-dos's README). A program is the
@@ -332,8 +336,8 @@ row's flags are its conventions: `-march=i486`, emulated thread-local storage
332
336
(there is no thread register the toolchain can address), unwind tables for
333
337
every unit, and the stack aligned to sixteen bytes at a call, as an i386 ok
334
338
image's is (the row's code calls images and is called by them). The provider's
335
-
link is `ld.lld -static --image-base=0x1000 -z norelro --gc-sections
336
-
--eh-frame-hdr`, entered at `okdos_entry`, over `base = "none"`, and
339
+
link is `ld.lld -static --image-base=0x1000 -z norelro -z stack-size=1048576
340
+
--gc-sections --eh-frame-hdr`, entered at `okdos_entry`, over `base = "none"`, and
337
341
the platform's tools it carries are the one its seal names (mcpp 2026.11.13.1):
338
342
a DOS build builds `okdos` alone, and an ok image does not build it. `mcpp run`
339
343
runs the program with dirun and xim's DOSBox Staging profile, which places
@@ -345,6 +349,13 @@ listed, resized and removed files and directories there (measured). openkal-dos
345
349
provides `abort`, `env`, `exec`, `fs`, `memory`, `stream`, `terminal` and
346
350
`time`. `region` is absent, because the DPMI host CWSDPMI is DPMI 0.90.
347
351
352
+
The stack (0.29.1) is the executable's statement: the row links with `-z
353
+
stack-size=1048576`, and openkal-dos 0.1.1's stub reads PT_GNU_STACK's size and
354
+
places the stack above a guard page (DPMI `0507h`), so an overflow is a reported
355
+
page fault rather than a write over the program. A project states another size
356
+
with its own link flags. Measured: 64 frames of 8 KiB return under DOSBox
357
+
Staging.
358
+
348
359
## Version group
349
360
350
361
`[platform.versions]` names one version of each package of the family. From
@@ -380,7 +391,7 @@ previous patch's.
380
391
|`checks/host-graph`| a build program runs as an ok image |
381
392
|`checks/snapshot`| a C++ program starts from a snapshot of its initialisers, and a start whose named value differs does not |
382
393
|`checks/i386`| an ok image of i386 is built in both modes, checked by okld and run by okrun built for i686-linux-musl; packed with `--systems dos-i686`, it runs as a DOS program |
383
-
|`checks/dos`| a program of i686-dos-musl runs in both modes under DOSBox Staging (technical experiment only) |
394
+
|`checks/dos`| a program of i686-dos-musl runs in both modes under DOSBox Staging, with a 512 KiB recursion, and states a 1 MiB stack (technical experiment only) |
384
395
| family release | the group's members are tagged and mirrored, both mcpp releases resolve an image of it, and a patch removes no symbol |
Copy file name to clipboardExpand all lines: mcpp.toml
+18-13Lines changed: 18 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@
12
12
[package]
13
13
namespace = "mcpplibs"
14
14
name = "openkal-platform"
15
-
version = "0.29.0"
15
+
version = "0.29.1"
16
16
description = "The platform of ok images (<arch>-openkal): their toolchain, C library and C++ run-time, tools, compile and link conventions, seal, runner and carrier, as one versioned statement mcpp reads."
17
17
license = "Apache-2.0"
18
18
authors = ["mcpplibs"]
@@ -82,7 +82,7 @@ okld = "openkal-tools@0.6.4"
82
82
okrun = "openkal-tools@0.6.4"
83
83
okprof = "openkal-tools@0.6.4"
84
84
# The seal of the DOS row (0.28.0): the stub of openkal-dos before an executable.
85
-
okdos = "openkal-dos-tools@0.1.0"
85
+
okdos = "openkal-dos-tools@0.1.1"
86
86
87
87
# Every unit of an image (SPEC 12.2):
88
88
# -fPIC the image is ET_DYN and has no text relocation;
@@ -239,7 +239,7 @@ hosted = true
239
239
base = "none"
240
240
toolchain = "llvm@23.1.3"
241
241
layers = { compiler-runtime = "openkal-llvm-runtime@0.20.3", "c++-abi" = "openkal-llvm-runtime@0.20.3", c-abi = { name = "openkal-musl", version = "0.29.8", default-features = false, features = ["posix", "malloc-mimalloc"] } }
0 commit comments