Define explicit volatile memory access for device registers

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

The issue says no volatile access contract was found in the inspected lexer, parser and memory API, but names no files or tests. Read those areas first and discuss the design with @LunaStev before implementation. Done means agreeing on the API or syntax, widths, alignment, target restrictions and observable access guarantees, then verifying optimized output and unsupported request diagnostics.

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

描述

discussion enhancement

Motivation

No source-level volatile load/store contract was found in the inspected lexer, parser and memory API. LLVM ordinary loads/stores and inline-assembly memory clobbers do not constitute a typed volatile access API.

Scope

Decide API or syntax, allowed widths/alignment and exact volatile access guarantees; keep volatile distinct from atomicity and synchronization. This is an optional systems capability, not a regression or proof of kernel suitability.

Completion criteria

  • Approve the source/API form and specify supported access widths, alignment and target restrictions.
  • Define preservation of observable accesses without claiming atomicity or synchronization.
  • Verify generated volatile accesses under optimization and diagnose unsupported requests explicitly.

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 摘要。