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
Ran your numbers, in your case it does not look like an endianess problem, and rather like a generic "reads across word boundaries" problem. I guess what happens is
bitvec reads from the start position until the end of the first word (00_0111)
this value is zeroextended to 0000_0111 (aka 0x7) and appended to the output
bitvec reads the remaining bits from the second word (01)
this value is shifted by 6 to 0100_0000 (aka 0x80), because the bitvec ended 6 bits before the end of the current word, and the result is appended to the output
@myrrlyn could you clarify what the expected output is? I guess there must be tests covering reads across word boundaries, therefore this behaviour might be intended (?)
Hello, if you run the below code you can see that while these should return the same value, the second instance returns
[0x7, 0x80]
.The text was updated successfully, but these errors were encountered: