fix: Match exact wide alias rejection across linkers #105
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-cstd!105
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/wide-string-link-rejection"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary and rationale
The wide core-only negative link now recognizes GNU and LLVM undefined-reference spellings and requires exactly all nineteen absent conventional aliases, with no missing/extra names or warnings. This fixes the expected-rejection witness in #98; it changes no wide-string implementation.
Tracking and scope
Quick CI repair for #98. Full memory-checker and guest acceptance remain separate.
Architecture, authority and failure behavior
No authority or ABI change: the existing actual native owner must still establish clean exit-one status and retirement. Source selection, public/hidden semantics, guard faults, original clocks and output limits remain intact.
Validation evidence
The maintained wide checker passed with explicitly selected GNU and LLVM host linkers: each exercised four semantic/guard executions, six actual SIGSEGV controls and the exact core-only negative link under the original 120/15-second lifetime and 30/15-second native limits. Two pure rejection-contract controls, syntax and Markdown checks pass. Runtime/header/Rust bodies and the native-owner cohort are unchanged; Rust build/Clippy gates are inapplicable to this Python witness change. No whole EriX or guest result is claimed.
The full-token parser follow-up rejects suffixed and newline-separated aliases. Its pure controls and both retained real linker diagnostics pass; those retained bytes are DATA, and the original native executions remain qualified to commit
619c14e.Review checklist