Define the freestanding memory-operation runtime contract

未关闭
#918 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
rust
领域
compilers

调研方向

Start with llvm/src/codegen/ir.rs at the linked starting point, then reproduce the O0/O2 object builds and inspect undefined symbols with llvm-nm. Discuss the design with @LunaStev before implementation. Done means the runtime ownership contract is documented, applied consistently to optimized loops and aggregate operations, and checked for overlapping memmove, zero-length operations, and unintended hosted linkage.

由索引模型根据 Issue 内容生成。

描述

discussion enhancement

Motivation

A raw byte-zeroing loop has no undefined symbol at O0, but O2 creates llvm.memset and the object has an undefined memset symbol. --freestanding disables default libc/libm links but does not prevent this lowering. This behavior is also common in C freestanding compilers; the gap is an explicit Wave ownership/provider contract.

Starting points: llvm/src/codegen/ir.rs.

fun clear(p: ptr<u8>, n: i64) { var i: i64 = 0; while (i < n) { deref p[i] = 0; i += 1; } }

Reproduced at 73aff59e on Linux amd64/LLVM 21.1.8: build with --freestanding --target=x86_64-unknown-none-elf --emit=obj at O0/O2, then inspect with llvm-nm --undefined-only. Only O2 has U memset in the sampled loop.

Scope

Decide compiler-owned memory helpers versus an explicit caller-supplied kernel runtime contract. Cover memcpy/memmove/memset and optimized loops/aggregates, including preservation of memory semantics.

Completion criteria

  • Agree on and document whether memory primitives are compiler-owned or explicitly provided by the freestanding environment.
  • Implement the approved contract consistently for optimized loops and aggregate copies/initialization.
  • Inspect O0/O2 undefined symbols and test overlapping memmove and zero-length operations without accidental hosted linkage.

Design required. Please mention @LunaStev to discuss the design before starting implementation.

主要语言
Rust
星标
56
派生
21
平均合并
23 小时 20 分钟
30 天内合并 PR
45

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

wavefnd/Wave 的其他 Issue

查看 wavefnd/Wave 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。