Skip to content

Handle non-numeric array indices for registers#92

Open
inferiorhumanorgans wants to merge 5 commits intoembassy-rs:mainfrom
inferiorhumanorgans:iho/non-numeric-array-indexes
Open

Handle non-numeric array indices for registers#92
inferiorhumanorgans wants to merge 5 commits intoembassy-rs:mainfrom
inferiorhumanorgans:iho/non-numeric-array-indexes

Conversation

@inferiorhumanorgans
Copy link

  • This gets hit when trying to parse the Renesas RA4M1 SVD
  • This doesn't respect the position of the index in the name (e.g. FOO%sBAR gets expanded to FOOBAR_%s)
  • This doesn't handle the non-register cases
  • This doesn't handle numeric indices where the start index is > 0

- This gets hit when trying to parse the Renesas RA4M1 SVD
- This doesn't respect the position of the index in the name
- This doesn't handle the non-register cases
- This doesn't handle numeric indices where the start index is > 0
@inferiorhumanorgans inferiorhumanorgans changed the title First pass at non-numeric array indices for registers Handle non-numeric array indices for registers Jan 5, 2026
Alex Zepeda added 4 commits January 4, 2026 20:23
This is useful for the case where multiple fieldsets are arrays with
explicit indices.  This is allowed at the IR level with the assumption
that the indices will be named and thus get unique accessors.  If
they're numbered we'll end up here.

E.g. Renesas RA4M1 USBFS::PIPE%sCTR.
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