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
Cpu_state inconsistency #1452
Comments
skalk
added a commit
to skalk/genode
that referenced
this issue
Mar 6, 2019
The initialization is surely the favored approach. I've changed and tested the ARM cpu_state accordingly in above commit. |
skalk
added a commit
to skalk/genode
that referenced
this issue
Mar 7, 2019
@chelmuth I've updated the commit according to your comment. |
chelmuth
pushed a commit
that referenced
this issue
Mar 7, 2019
chelmuth
pushed a commit
that referenced
this issue
Mar 7, 2019
chelmuth
pushed a commit
that referenced
this issue
Mar 7, 2019
trimpim
pushed a commit
to trimpim/genode
that referenced
this issue
May 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
Cpu_state
class in cpu/cpu_state.h is defined slightly inconsistent across CPU architectures. In base/include/arm/cpu/cpu_state.h, all member variables are uninitialized whereby in base/include/x86_32/cpu/cpu_state.h and base/include/x86_64/cpu/cpu_state.h, all member variables are initialized with 0. Which approach is correct?The text was updated successfully, but these errors were encountered: