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
When dashmips stores a value in a register, it's stored as decimal. This is a problem when storing memory addresses for later.
Say I stored a memory address 0x8000 0046. If I increment this by 4, the address I'm looking to reach is 0x8000 004a. Instead I end up getting 0x8000 0050.
It's possible that there's a setting to change this but I couldn't find it anywhere.
The text was updated successfully, but these errors were encountered:
Hey thanks for reaching out, can you share the snippet of mips incrementing the address/value in the register?
The values in registers are stored as python integers so I would expect the math to not be dependent on decimal vs hex formatting. Perhaps there is a printing issue while the runtime values are correct?
When dashmips stores a value in a register, it's stored as decimal. This is a problem when storing memory addresses for later.
Say I stored a memory address 0x8000 0046. If I increment this by 4, the address I'm looking to reach is 0x8000 004a. Instead I end up getting 0x8000 0050.
It's possible that there's a setting to change this but I couldn't find it anywhere.
The text was updated successfully, but these errors were encountered: