From f35f91b8e1f60bf2fd61df5163bb7c9025de5339 Mon Sep 17 00:00:00 2001
From: sunrisepeak <speakshen@163.com>
Date: Sat, 3 Oct 2026 02:35:11 +0800
Subject: [PATCH] 0.20.1 --- openkal-linux 0.16.1 beneath

The pin moves and nothing else does. 0.16.1 repairs where openkal-linux copies
the program's thread-local image (found by openkal-llvm-runtime's own probe
against 0.16.0), and this port is what reaches that implementation: a version
written without an operator is an exact pin in mcpp, so a consumer naming this
C library and the implementation it runs on names one of each and not two.

Nothing in this package changes with it. The region a context stands on was
measured before the repair and is measured the same way after it, and
`examples/stack-bounds` reports the same three readings.
---
 README.md | 2 +-
 mcpp.toml | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index fd0814d..b234d14 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ the claim can be checked rather than repeated.
 
 ```toml
 [dependencies]
-openkal-musl = "0.20.0"
+openkal-musl = "0.20.1"
 ```
 
 > **Engine floor (mcpp 2026.9.18.3):** this version of this package declares
diff --git a/mcpp.toml b/mcpp.toml
index 46ac006..044d520 100644
--- a/mcpp.toml
+++ b/mcpp.toml
@@ -1,7 +1,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-musl"
-version     = "0.20.0"
+version     = "0.20.1"
 description = "musl 1.2.5 redirected onto openkal: one C library, ported once, above every implementation of the specification rather than above one kernel."
 license     = "Apache-2.0"
 
@@ -178,7 +178,7 @@ openkal = "0.15.0"
 #
 # The consequence for a program is that it names this package and nothing else.
 [target.'cfg(os = "linux")'.dependencies]
-openkal-linux = { version = "0.16.0", features = ["standalone"] }
+openkal-linux = { version = "0.16.1", features = ["standalone"] }
 
 [target.'cfg(os = "macos")'.dependencies]
 # 0.12.0 is the first release of this implementation that declares which