meme / aarch64-extensions Goto Github PK

Currently all new instructions are added into the single aarch64_extensions.cpp file. Instead, we should compartmentalize the instruction lifters and their helpers into categories.

See list of system registers, as well

Binary Ninja will detect it as an incoming register otherwise (and will choke analysis)

Thanks to the changes in #3, we have added some tests for the FMOV instruction. Now, it would make sense to flesh out a test suite for all of the instructions supported by this lifter and ensure that instructions are lifted properly.

Currently they are lifted as a constant, corresponding to the internal Capstone disassembler constant. It would be nice if we could either actually print the register name or print the name as a string instead.

Use GitHub Actions to build the extension on CI and upload release artifacts to end-users for tagged releases.

Potentially may require uploading an encrypted libbinaryninjacore.so.1 to GH, ideally we can figure out how to disable errors on undefined symbols?