[FEATURE] Exercise current-locale C calls in a dedicated native image #605

Open
opened 2026-11-08 14:36:59 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

The conventional C locale runtime has a separate native process profile, but the maintained image scenarios and C-startup metadata still select the legacy startup program. Reusing that program's identity or treating a compiled fixture as guest execution would not demonstrate the new runtime.

Proposed behavior and scope

Add a closed native image and VM scenario for the original realm-c-locale-client profile. Select its genuine source, entry, C fixture, process product and guest launch path. Explicitly enable Loaderd's thread-runtime-state feature and retain its versioned capacity contract. Extend source/product/metadata admission and runtime program selection together. Preserve the old C-startup scenario, source roles, argv, program selection and default 32-byte TCB. Update Rootd or Kernel consumers in matching feature branches if their closed program declarations require it.

Authority, security and reliability

The same original process/source/native operation owners retain compilation, file, launch, mapping and retirement duties. Profile names, runtime bits, markers and metadata describe selection; they cannot establish process or thread authority. The new stream-based startup route receives no invented byte-thread factory, group, namespace or unused endpoint authority. Bind actual extended initial state before conventional calls. Reject mismatched source/entry/product/profile, feature-off Loaderd and malformed capacity metadata before native effects where possible. Preserve original errors and uncertain cleanup rather than retrying or relabelling an older artifact.

Acceptance criteria

  • Add an explicit closed scenario and runtime program selection with matching source/product/metadata admission and complete graph wiring.
  • Select the actual extended Loaderd feature and derive packet/workspace capacity from its complete descriptor.
  • Run the original locale and conversion C probes through the genuine startup root; distinguish the selected workload and collect its actual result.
  • Cover wrong profile/source/entry/product, absent feature/provider, malformed descriptor and original failure/cleanup paths without changing older oracles or limits.
  • Document the matching component, image, guest and authority contracts.
  • Build and execute the selected image through original native and VM owners, including real state initialization and positive process retirement; retain older startup regression acceptance.

Alternatives and tradeoffs

Retagging the old C-startup program hides a different source and ABI. Building both programs without explicit guest selection leaves the workload unproven. A separate closed scenario makes the actual consumer and extended image requirement reviewable while sharing maintained startup and image machinery.

Tracking and rollout

Companion native current-locale compiler, Posixd process profile, conventional conversion design and thread-state design. Complete the source/consumer scenario together before launching a fresh original-budget image and VM operation. Additional native thread creation remains a separate acceptance obligation.

## Problem and motivation The conventional C locale runtime has a separate native process profile, but the maintained image scenarios and C-startup metadata still select the legacy startup program. Reusing that program's identity or treating a compiled fixture as guest execution would not demonstrate the new runtime. ## Proposed behavior and scope Add a closed native image and VM scenario for the original realm-c-locale-client profile. Select its genuine source, entry, C fixture, process product and guest launch path. Explicitly enable Loaderd's thread-runtime-state feature and retain its versioned capacity contract. Extend source/product/metadata admission and runtime program selection together. Preserve the old C-startup scenario, source roles, argv, program selection and default 32-byte TCB. Update Rootd or Kernel consumers in matching feature branches if their closed program declarations require it. ## Authority, security and reliability The same original process/source/native operation owners retain compilation, file, launch, mapping and retirement duties. Profile names, runtime bits, markers and metadata describe selection; they cannot establish process or thread authority. The new stream-based startup route receives no invented byte-thread factory, group, namespace or unused endpoint authority. Bind actual extended initial state before conventional calls. Reject mismatched source/entry/product/profile, feature-off Loaderd and malformed capacity metadata before native effects where possible. Preserve original errors and uncertain cleanup rather than retrying or relabelling an older artifact. ## Acceptance criteria - [ ] Add an explicit closed scenario and runtime program selection with matching source/product/metadata admission and complete graph wiring. - [ ] Select the actual extended Loaderd feature and derive packet/workspace capacity from its complete descriptor. - [ ] Run the original locale and conversion C probes through the genuine startup root; distinguish the selected workload and collect its actual result. - [ ] Cover wrong profile/source/entry/product, absent feature/provider, malformed descriptor and original failure/cleanup paths without changing older oracles or limits. - [ ] Document the matching component, image, guest and authority contracts. - [ ] Build and execute the selected image through original native and VM owners, including real state initialization and positive process retirement; retain older startup regression acceptance. ## Alternatives and tradeoffs Retagging the old C-startup program hides a different source and ABI. Building both programs without explicit guest selection leaves the workload unproven. A separate closed scenario makes the actual consumer and extended image requirement reviewable while sharing maintained startup and image machinery. ## Tracking and rollout Companion [native current-locale compiler](https://git.erikinkinen.fi/erix/integration/pulls/601), [Posixd process profile](https://git.erikinkinen.fi/erix/posixd/pulls/155), [conventional conversion design](https://git.erikinkinen.fi/erix/lib-cstd/issues/87) and [thread-state design](https://git.erikinkinen.fi/erix/lib-cstd/issues/85). Complete the source/consumer scenario together before launching a fresh original-budget image and VM operation. Additional native thread creation remains a separate acceptance obligation.
erikinkinen added this to the Alpha 1 milestone 2026-11-08 14:36:59 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#605
No description provided.