ssm issueshttps://gitlab.science.ru.nl/compilerconstruction/ssm/-/issues2022-05-16T07:21:53+02:00https://gitlab.science.ru.nl/compilerconstruction/ssm/-/issues/5Hex constants are not parsed correctly2022-05-16T07:21:53+02:00Mart LubbersHex constants are not parsed correctlyreported by Steven Bronswijk
```
ldc 0x10
ldc 0x1A
halt
```
0x1A is not parsed correctlyreported by Steven Bronswijk
```
ldc 0x10
ldc 0x1A
halt
```
0x1A is not parsed correctlyhttps://gitlab.science.ru.nl/compilerconstruction/ssm/-/issues/3Make clear that constant 0 is not read by the interpreter correctly, and that...2021-01-25T11:50:00+01:00Ward TheunisseMake clear that constant 0 is not read by the interpreter correctly, and that you need to write 00 to get constant 0.https://gitlab.science.ru.nl/compilerconstruction/ssm/-/issues/1Make the documentation available online2021-01-25T11:33:55+01:00Mart LubbersMake the documentation available onlineMart LubbersMart Lubbershttps://gitlab.science.ru.nl/compilerconstruction/ssm/-/issues/4Return code is zero even when the interpreter errors out2021-03-22T14:37:38+01:00Mart LubbersReturn code is zero even when the interpreter errors outMart LubbersMart Lubbershttps://gitlab.science.ru.nl/compilerconstruction/ssm/-/issues/2Wrong documentation for LDAA2020-05-25T14:09:01+02:00Reinier Joosser.joosse@student.science.ru.nlWrong documentation for LDAAIn the documentation in the GUI for the LDAA instruction (Help, Help on Topic, LDAA) there appears to be an error.
It currently says this:
```
Description
Load Address of Address. Pushes the address of a value relative to the address on...In the documentation in the GUI for the LDAA instruction (Help, Help on Topic, LDAA) there appears to be an error.
It currently says this:
```
Description
Load Address of Address. Pushes the address of a value relative to the address on top of the stack. This instruction effectively adds a constant to the top of the stack.
Pre and Post State
SP_post = SP_pre + 1
M_post[SP_post] = M_pre[SP_pre] + M_pre[PC_pre+1]
```
But actually, it doesn't push a new value onto the stack on top of the old one. Instead, it increments the value on top of the stack with the argument of LDAA. So the stack size does not increase.
So the actual pre and post states are:
```
SP_post = SP_pre
M_post[SP_post] = M_pre[SP_pre] + M_pre[PC_pre+1]
```
Changing the documentation (and not the implementation of LDAA) seems like the best option to me, since the way it currently actually works seems the most logical and it fits in with how similar operations work.