Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find/use documentation on metabits of AE registers #59

Open
jamesyoungman opened this issue May 2, 2022 · 2 comments
Open

Find/use documentation on metabits of AE registers #59

jamesyoungman opened this issue May 2, 2022 · 2 comments

Comments

@jamesyoungman
Copy link
Contributor

The AE registers (A, B, C, D) are stored in the Arithmetic Element. E is stored in the Exchange Element, but is also described as an Arithmetic Element register. They are mapped into the Vff memory range.

I have a fuzzy recollection that they don't have metabits and so netabit operations take effect on the M register but have no effect on the actual AE registers themselves. But I can't right now find a spot in the documentation that talks about this.

The necessary action here is to find the relevant documentation and add tests relating to it. For example use of the SKM instuction on the addresses corresponding to some of the AE registers.

@jamesyoungman
Copy link
Contributor Author

jamesyoungman commented May 2, 2022

There is a mention of this on page 5-23 of the Users Handbook (which describes the Sync System, which is what the "can be detected" phrase refers to):

The data reference metabit (M⁴𛲄¹⁰) can be detected only when set (just as N⁴𛲄¹⁰). Note that it can be changed without a memory reference for it serves as the metabit of the A, B, C, D, and E registers. (i.e., MKC₄.₁₀ A or MKC₄.₁₀ B will change bit 4.10 of M).

@jamesyoungman
Copy link
Contributor Author

If the AE registers share a metabit (in M) then we will likely need a struct attribute somewhere which holds the value of M, and will need to integrate this with the working of the exchange element code (which up to now has been stateless).

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

No branches or pull requests

1 participant