0.13.4 --- carry openkal-macos 0.9.1 and openkal-windows 0.7.4 - #33
Merged
Merged
Conversation
openkal-macos 0.9.1: every program built with --release faulted before main, because the system call wrapper declared x1 an input only and this kernel returns a second value there. openkal-windows 0.7.4: environment values were reported with forward slashes, so a program given a changed environment could not run anything through the command interpreter. Both requirements are exact, so consumers reach the fixes through this release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Carries two fixes from the platform implementations beneath this library. Both requirements here are exact, so consumers of openkal-musl reach them only through this release.
openkal-macos 0.9.1 (0.9.1 --- the second register comes back from every call openkal-macos#20, mcpp-index#421): every program built with
--releasefaulted inkal_fs_preopen, called from this library's initializer, beforemain. The system call wrapper declared x1 an input only, this kernel returns a second value there, and an optimizing compiler kept an argument in it across the call. Found through lsp-mcpp, whose release server and a minimalimport stdprogram over openkal-llvm-runtime 0.9.4 both stopped there on macos-14.openkal-windows 0.7.4 (0.7.4 --- a named value is reported as it was set openkal-windows#23, mcpp-index#421): environment values were reported with forward slashes, so a program given a changed environment received
ComSpec=C:/Windows/system32/cmd.exeand every command run through the interpreter failed.openkal-macos = "0.9.1",openkal-windows = "0.7.4", version 0.13.4.README.md: 0.13.4 is carried byopenkal-llvm-runtime = "0.9.5".The existing rows run the probes on both hosts; openkal-macos's own CI now runs its tests in the release profile, which is where the macOS defect showed.