Skip to content

Bump yscope clp core#1

Open
Bill-hbrhbr wants to merge 2 commits into
y-scope:mainfrom
Bill-hbrhbr:bump-yscope-clp-core
Open

Bump yscope clp core#1
Bill-hbrhbr wants to merge 2 commits into
y-scope:mainfrom
Bill-hbrhbr:bump-yscope-clp-core

Conversation

@Bill-hbrhbr

Copy link
Copy Markdown
Collaborator

No description provided.

FindHao and others added 2 commits May 31, 2026 15:34
Summary:
Bring `validation/schemas/` in sync with the trace writer. `SCHEMAS_BY_TYPE` previously mapped only `reg_trace` / `mem_trace` / `opcode_only` / `kernel_metadata`, but the writer also emits `mem_value_trace`, `mem_addr_trace`, and `tma_trace` — none of which had a schema, so `validate` / `compare` silently skipped every current trace's data records.

New schemas (field sets verified against the serializers and a real trace):
- `tma_trace.schema.json`: version-union — only the common fields are required; the descriptor fields are writer-variant-dependent and optional (the current writer emits `tma_param_size` + `tma_transfer_info` + `desc_addr`; older traces emit `desc_addr` + `desc_raw`, 16 hex-string qwords). Accepting both keeps the schema valid across writer versions.
- `mem_value_trace.schema.json`: `ipoint:"A"`, `mem_space`, `is_load`, `access_size`, `addrs[32]`, `values[32][1..4]` (the old `mem_trace.schema.json` only had `addrs`).
- `mem_addr_trace.schema.json`: `ipoint:"B"`, `addrs[32]`.

`schema_loader.py` loads the three and registers them in `SCHEMAS_BY_TYPE` (`mem_trace` kept for backward compatibility); `validation/__init__.py` re-exports them.

Reviewed By: wlei-llvm

Differential Revision: D106872962

fbshipit-source-id: 6497b94546804b29c1d08ebbba7b1fccd2b66f15
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.

2 participants