V5 Fix big endian and 32bit builds#2943
Conversation
Rot127
left a comment
There was a problem hiding this comment.
Would you mind also applying the other changes from https://github.com/capstone-engine/capstone/pull/2796/changes#diff-8ab50bbaa9a6956702fed253c6b8d13be8f3c4b062faf4398af2053c731e9e82
There are not that many. Mostly formatting changes for the three archs here. Simply copy and paste should do the job.
Co-authored-by: Rot127 <45763064+Rot127@users.noreply.github.com>
Co-authored-by: Rot127 <45763064+Rot127@users.noreply.github.com>
|
done. do u want me to rewrite the history in separate commits for clarity about fixes/features or do you prefer to do that yourself? |
Rot127
left a comment
There was a problem hiding this comment.
/usr/lib/gcc-cross/mips-linux-gnu/12/../../../../mips-linux-gnu/bin/ld: /tmp/ccHbECYk.o: in function `set_function':
capstone_test.c:(.text+0xee4): undefined reference to `get_detail_sh'
collect2: error: ld returned 1 exit status
It doesn't look like cstest is build successfully.
And the report.py script just ignores that :(
v5 testing is pretty broken...
|
Sorry for the mess, but it seems like it's finally going well now |
|
Sadly not :(
Not really your fault. The testing in v5 is just not nice to use. |
|
Only one left: Check out my 32bit PR for the next branch. |
|
good now? |
|
Thanks, will do a last swipe tomorrow. |
|
The commit history is messed up with random fixes here and there, will you squash or want to me remake the commits in a clean way? |
|
We squash here normally. I fixed the commit message. |
i backported the crossbuilds ci jobs from the next branch to the v5 one.
that confirmed the bugs i found that are already fixed in v6, so i just fixed them here and added more tests: