Skip to content

[codex] Normalize linx-model fixture naming across docs and codec tooling#2

Merged
zhoubot merged 1 commit into
mainfrom
codex/model-llvm-elf-fixtures
May 16, 2026
Merged

[codex] Normalize linx-model fixture naming across docs and codec tooling#2
zhoubot merged 1 commit into
mainfrom
codex/model-llvm-elf-fixtures

Conversation

@zhoubot
Copy link
Copy Markdown
Contributor

@zhoubot zhoubot commented May 16, 2026

What changed

  • normalize the LLVM ELF minst fixture naming in docs and build metadata
  • keep the codec generator and emitted minst record labels consistent with that naming

Why

The superproject documentation now refers to the fixture path consistently, and the model repo needs to match that surface.

Impact

This keeps the lightweight model/docs lane consistent with the rest of the bring-up documentation stack.

Validation

  • no dedicated linx-model regression rerun in this publish turn

The superproject now refers to the LLVM ELF minst fixture path consistently,
so the model repo needs its docs, generator wording, and emitted record labels
to match. This keeps the lightweight model references aligned with the rest of
the bring-up documentation and tooling.

Constraint: Superproject bring-up docs now use the LLVM ELF fixture naming consistently
Rejected: Keep the legacy names in model docs and codec code | leaves the model surface inconsistent with the active bring-up docs
Confidence: medium
Scope-risk: narrow
Directive: Keep minst fixture names synchronized between documentation and generator output
Not-tested: No dedicated linx-model build or regression rerun in this publish turn
@zhoubot zhoubot merged commit d893d7a into main May 16, 2026
10 checks passed
@zhoubot zhoubot deleted the codex/model-llvm-elf-fixtures branch May 16, 2026 06:47
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the LinxISA version from v0.4 to v0.56 across the build system, documentation, and source code. Feedback was provided regarding hardcoded absolute paths in the documentation and the codec generation script, which hinder portability; specifically, it was suggested to make the --spec argument required in the script rather than relying on a user-specific default path.

parser.add_argument(
"--spec",
default="/Users/zhoubot/linx-isa/isa/v0.4/linxisa-v0.4.json",
default="/Users/zhoubot/linx-isa/isa/v0.56/linxisa-v0.56.json",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The default value for the --spec argument is a hardcoded absolute path to a specific user's home directory. This makes the script non-portable. Since the build system (CMakeLists.txt) already provides this path explicitly, it is better to remove the default and make the argument required to avoid accidental use of an invalid path.

Suggested change
default="/Users/zhoubot/linx-isa/isa/v0.56/linxisa-v0.56.json",
required=True,

Comment thread docs/isa.md
The source of truth is:

- `/Users/zhoubot/linx-isa/isa/v0.4/linxisa-v0.4.json`
- `/Users/zhoubot/linx-isa/isa/v0.56/linxisa-v0.56.json`
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The path to the ISA specification is hardcoded as an absolute path to a specific user's home directory (/Users/zhoubot/...). This should be updated to a relative path or a generic placeholder to ensure it is accurate for all developers and environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant