We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In Python, the result of int/int is the float type and the size is as same as the float in C/C++. However, the int type in Python is unbounded. Thus, conversion from floating point to integer may round or truncate as in C.
int/int
Calculating of cache line aligned address:
witcher/replay/mem/cachenumbers.py
Lines 8 to 9 in ad69038
calculating of atomic-size aligned address:
witcher/replay/mem/witchertrace.py
Lines 43 to 44 in ad69038
If the address starts with 0xf, the result is incorrect after the calculation.
0xf
aligned_addr = address // ALIGNMENT_NUM * ALIGNMENT_NUM
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue:
In Python, the result of
int/int
is the float type and the size is as same as the float in C/C++. However, the int type in Python is unbounded. Thus, conversion from floating point to integer may round or truncate as in C.Affected code:
Calculating of cache line aligned address:
witcher/replay/mem/cachenumbers.py
Lines 8 to 9 in ad69038
calculating of atomic-size aligned address:
witcher/replay/mem/witchertrace.py
Lines 43 to 44 in ad69038
If the address starts with
0xf
, the result is incorrect after the calculation.Fixes:
The text was updated successfully, but these errors were encountered: