Open qtiuto opened 5 years ago
Is this what you see?
minilua dynasm\dynasm.lua -LN -o t.h call_arm.dasc
call_arm.dasc:87: error: bad immediate `L':
|.long L, ref, LUA_REGISTRYINDEX
call_arm.dasc:110: error: bad immediate `mt':
| load32 r2, mt
| .long val [MACRO load32 (2)]
call_arm.dasc:123: error: bad immediate `mt':
| load32 r2, mt
| .long val [MACRO load32 (2)]
call_arm.dasc:137: error: bad immediate `mt':
| load32 r2, mt
| .long val [MACRO load32 (2)]
call_arm.dasc:217: error: bad immediate `mt':
| load32 r3, mt
| .long val [MACRO load32 (2)]
...
If not - what do you get?
Looks like it may be because there was a local change to dynasm by James McKaskill:
https://github.com/facebookarchive/luaffifb/commit/cdbfbc7fb558fe66d347e61b3a7e7e88f473b744
When I updated to 1.4 this got lost ... however I am not sure whether this is the right way to do it.
Yes, that's what I got. I want to migrate luaffi to android, and I will still try.
Dibyendu Majumdar notifications@github.com 于 2019年1月1日周二 23:21写道:
Looks like it may be because there was a local change to dynasm by James McKaskill:
facebookarchive@cdbfbc7 https://github.com/facebookarchive/luaffifb/commit/cdbfbc7fb558fe66d347e61b3a7e7e88f473b744
When I updated to 1.4 this got lost ... however I am not sure whether this is the right way to do it.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dibyendumajumdar/ravi-ffi/issues/12#issuecomment-450737530, or mute the thread https://github.com/notifications/unsubscribe-auth/AJHwUn6tQ38DU_M7CmM_8Zi7Tlny19CWks5u-3z0gaJpZM4Zl7Hi .
Okay, I will try to apply the change I mentioned above tonight. Hopefully that will fix it.
dyasm 1.4.0 doesn't seem to support call_arm.dasc