summaryrefslogtreecommitdiff
path: root/docs/dev/archplatform-lifting.md
diff options
context:
space:
mode:
authorJordan Wiens <github@psifertex.com>2026-03-14 09:28:34 -0400
committerJordan Wiens <github@psifertex.com>2026-03-14 09:28:34 -0400
commit7141a9061b1c6ebffb63da75bfa964ada3a6a27f (patch)
treeecab8357340e5adf2a92e903bc62373d3394cc15 /docs/dev/archplatform-lifting.md
parenta12d2e1d8c8f15c603a4b40ff0bce9473ba64063 (diff)
add mentions of the final github repo earlier in the quark series
Diffstat (limited to 'docs/dev/archplatform-lifting.md')
-rw-r--r--docs/dev/archplatform-lifting.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/archplatform-lifting.md b/docs/dev/archplatform-lifting.md
index 4bb7937a..316270d0 100644
--- a/docs/dev/archplatform-lifting.md
+++ b/docs/dev/archplatform-lifting.md
@@ -1,6 +1,6 @@
# Lifting
-Lifting is the critical step to unlocking Binary Ninja's powerful analysis and decompilation. Often the "left as an exercise to the reader" of Binary Ninja custom architecture tutorials, it is both a lengthy process and one with a lot of subtlety. From simple instructions to flags and intrinsics, the lifting process describes the behavior of every instruction. Let's write a lifter for [Quark](archplatform-disassembly.md#target)!
+Lifting is the critical step to unlocking Binary Ninja's powerful analysis and decompilation. Often the "left as an exercise to the reader" of Binary Ninja custom architecture tutorials, it is both a lengthy process and one with a lot of subtlety. From simple instructions to flags and intrinsics, the lifting process describes the behavior of every instruction. Let's write a lifter for [Quark](archplatform-disassembly.md#target)! The complete source code is available at [arch_quark on GitHub](https://github.com/Vector35/arch_quark).
To write a lifter, we need to implement `get_instruction_low_level_il`. The lifter needs the same information as the disassembler, so the scaffolding is very similar: