You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tools/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,9 +212,9 @@ CSR selector properties:
212
212
- Both accept decimal integer, hex string (`0x...`), or binary string (`0b...`).
213
213
214
214
Notes on output behavior:
215
-
- JSON output copies the authored `enum` object into the generated `csrs` entry.
215
+
- JSON output preserves the structure of the authored `enum` object in the generated `csrs` entry, but normalizes any multibase numeric values (for example hex `0x...` or binary `0b...`) to plain integers.
216
216
- JSON output stores `ro-mask`/`ro-value` as integers.
217
-
- HTML output preserves the original authored literal text for `ro-mask`/`ro-value` when available (for example `0xF0F0` or `0b1100`).
217
+
- HTML output uses internal underscore-prefixed fields to preserve the original authored literal text for `enum` values and `ro-mask`/`ro-value` when available (for example `0xF0F0` or `0b1100`).
fatal(f"CSR {representative_name} in {def_filename} has invalid illegal-write-return: {raw_illegal_return!r}; expected integer, hex string, or binary string")
0 commit comments