[FEATURE] Supply matching C++ runtime sources for the EriX toolchain #608

Open
opened 2026-11-08 15:27:29 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

The LLVM toolchain recipes request libc++ and libc++abi, but the admitted Rust source archive omits them. The selected Rust fork and LLVM 21.1.8 release have identical libc++, libc++abi, common CMake and runtimes Git subtrees. Their libunwind subtrees differ, so replacing the whole fork would change an already selected source.

Proposed behavior and scope

Admit the official LLVM 21.1.8 libc++ and libc++abi release archives through the existing bounded source-input protocol. Verify complete bytes and matching project trees, retain legal identities, and declare their use in the external toolchain source layout. Preserve Rust's selected libunwind. Make the target C++ runtime choice explicit in the cross and guest recipe inputs; retain the separate Linux bootstrap runtime. Keep unresolved target/sysroot/patch and deployment requirements explicit before execution.

Authority, security and reliability

Use original download, archive and layout receivers; digests, tree IDs, URLs and recipe records are data rather than source authority. Reject wrong bytes, unsafe members, mismatched trees, absent notices and partial/uncertain retirement. Keep imported runtime implementation outside trusted EriX repositories and native service dependencies. Target include/library paths must not fall back to host libraries. Preserve localization, wide-character, Unicode, thread, filesystem, exception and RTTI requirements instead of disabling them to obtain a smaller build.

Acceptance criteria

  • Authenticate both archive bodies against primary release metadata and verify complete selected subtree contents and modes through original finite inputs.
  • Retain exact project licenses and relevant file notices in source declarations and offline payload metadata.
  • Bind explicit runtime source roots in the maintained toolchain declarations and layout without overwriting the Rust archive or replacing its libunwind.
  • Declare target libc++/libc++abi, compiler-rt and unwinder choices, including required runtime-first ordering; reject unresolved port/sysroot/deployment inputs before build effects.
  • Cover wrong digest/tree/member, missing legal/input bindings, partial failure and original retirement; document source and configuration contracts.
  • Verify the resulting source closure before actual target runtime builds and the full in-EriX toolchain rebuild.

Alternatives and tradeoffs

A full upstream LLVM replacement loses Rust's libunwind changes. Reusing Linux libstdc++ changes the target runtime and does not supply an EriX port. Two matching release archives supply the missing project trees while preserving the selected compiler fork. Static/shared deployment still needs an explicit decision backed by the actual EriX loader and unwind contracts.

Tracking and rollout

Follow the upstream interface mapping and maintained toolchain inputs. Complete source admission and declarations first. Target libc/std ports, runtime builds, guest execution and the complete toolchain rebuild remain required acceptance.

## Problem and motivation The LLVM toolchain recipes request libc++ and libc++abi, but the admitted Rust source archive omits them. The selected Rust fork and LLVM 21.1.8 release have identical libc++, libc++abi, common CMake and runtimes Git subtrees. Their libunwind subtrees differ, so replacing the whole fork would change an already selected source. ## Proposed behavior and scope Admit the official LLVM 21.1.8 libc++ and libc++abi release archives through the existing bounded source-input protocol. Verify complete bytes and matching project trees, retain legal identities, and declare their use in the external toolchain source layout. Preserve Rust's selected libunwind. Make the target C++ runtime choice explicit in the cross and guest recipe inputs; retain the separate Linux bootstrap runtime. Keep unresolved target/sysroot/patch and deployment requirements explicit before execution. ## Authority, security and reliability Use original download, archive and layout receivers; digests, tree IDs, URLs and recipe records are data rather than source authority. Reject wrong bytes, unsafe members, mismatched trees, absent notices and partial/uncertain retirement. Keep imported runtime implementation outside trusted EriX repositories and native service dependencies. Target include/library paths must not fall back to host libraries. Preserve localization, wide-character, Unicode, thread, filesystem, exception and RTTI requirements instead of disabling them to obtain a smaller build. ## Acceptance criteria - [ ] Authenticate both archive bodies against primary release metadata and verify complete selected subtree contents and modes through original finite inputs. - [ ] Retain exact project licenses and relevant file notices in source declarations and offline payload metadata. - [ ] Bind explicit runtime source roots in the maintained toolchain declarations and layout without overwriting the Rust archive or replacing its libunwind. - [ ] Declare target libc++/libc++abi, compiler-rt and unwinder choices, including required runtime-first ordering; reject unresolved port/sysroot/deployment inputs before build effects. - [ ] Cover wrong digest/tree/member, missing legal/input bindings, partial failure and original retirement; document source and configuration contracts. - [ ] Verify the resulting source closure before actual target runtime builds and the full in-EriX toolchain rebuild. ## Alternatives and tradeoffs A full upstream LLVM replacement loses Rust's libunwind changes. Reusing Linux libstdc++ changes the target runtime and does not supply an EriX port. Two matching release archives supply the missing project trees while preserving the selected compiler fork. Static/shared deployment still needs an explicit decision backed by the actual EriX loader and unwind contracts. ## Tracking and rollout Follow the [upstream interface mapping](https://git.erikinkinen.fi/erix/lib-cstd/pulls/88) and [maintained toolchain inputs](https://git.erikinkinen.fi/erix/integration/pulls/595). Complete source admission and declarations first. Target libc/std ports, runtime builds, guest execution and the complete toolchain rebuild remain required acceptance.
erikinkinen added this to the Alpha 1 milestone 2026-11-08 15:27:29 +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#608
No description provided.