-
Notifications
You must be signed in to change notification settings - Fork 6
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
More explicit operand size #9
Comments
Very nice update. I just checked running ELKS again on it and the c)continuous trace output is nicely improved! On another note, I have been considering whether is makes sense to show when a hardware interrupt occurs, when in instruction tracing mode. The idea is that, since the instruction stream can't show a (hardware-only) interrupt address being pushed on the stack, one cannot actually tell that one has occurred, other than knowing the interrupt vector address and noticing it has suddenly changed. I was thinking something like the following line inserted in exec_int():
What do you think? [EDIT: the intention was to show ONLY hardware interrupts, not executed INT instructions... so the above won't quite work. Perhaps the printf could be in a function like hw_int() that then calls exec_int().] |
Review of all operation classes completed. Closing this issue. |
See #8 comments
The size of the operand is explicit for string operations with 'BYTE' or 'WORD' qualifiers, but only given though an hint based on the number of digits when displaying an immediate value. Improve the display to be more explicit, in both Intel and AT&T syntax.
The text was updated successfully, but these errors were encountered: