update readme

README.md

@@ -6,7 +6,7 @@ This tool is designed for:
 
 ## Building
 
-To build the project, take a look at **docs/BUILDING.md**.
+To build the project, take a look at [**docs/BUILDING.md**](https://github.com/NaC-L/Mergen/blob/main/docs/BUILDING.md).
 
 ## Core Objectives:
 
@@ -47,7 +47,7 @@ VMProtect settings, everything is turned off, we virtualize the function on ultr
 
 Here, we run mergen. First argument is the name of the file and the second argument is the address of the function. Look how simple it is to run. And we can compile the output so we can explore it using our favorite decompiler.
 
-![image](images/run_mergen.png)
+![image](images/run_mergen.PNG)
 
 ```llvm
 ; ModuleID = 'my_lifting_module'
@@ -82,10 +82,80 @@ define i64 @main(i64 %rcx, i64 %rdx, i64 %rdx, i64 %r8, i64 %r9 ...)
 ```
 So, we just adjust the function signature to look normally. If you have more questions about this part, I suggest you research [calling conventions](https://learn.microsoft.com/en-us/cpp/build/x64-calling-convention?view=msvc-170#parameter-passing) and [ABI](https://learn.microsoft.com/en-us/cpp/build/x64-software-conventions?view=msvc-170&source=recommendations#register-volatility-and-preservation).
 
+## Branches/Jumptables
+So, lets say we have this code. VM's will take this, and turn into a jump table so its harder to find the branch.
+```cpp
+int maths(int a, int b, int c) {
+    if (a > b)
+        return a + b + c;
+    else
+        return a - b - c;
+}
+```
+
+This would be a high level interpretation of it. If you want to see how it really works, you can check [this file](https://github.com/NaC-L/Mergen/blob/main/teststuff/test_branches.asm).
+
+```
+...
+next_handler = xxx;
+if ( a-b > 0 )
+  next_handler = yyy;
+jump next_handler;
+...
+
+```
+This is how it will look when Mergen is running, it will execute a _very_ simple dependency analysis to find the "key" value and ask you to select a possible value. 
+![image](images/branches_0.png)
+
+Output will look like this:
+```llvm
+; ModuleID = 'my_lifting_module'
+source_filename = "my_lifting_module"
+
+; Function Attrs: mustprogress nofree norecurse nosync nounwind willreturn memory(none)
+define i64 @main(i64 %rax, i64 %rcx, i64 %rdx, i64 %rbx, i64 %rsp, i64 %rbp, i64 %rsi, i64 %rdi, i64 %r8, i64 %r9, i64 %r10, i64 %r11, i64 %r12, i64 %r13, i64 %r14, i64 %r15, ptr nocapture readnone %memory) local_unnamed_addr #0 {
+entry:
+  %stackmemory = alloca i128, i128 13758960, align 8
+  %0 = trunc i64 %r8 to i32
+  %1 = trunc i64 %rdx to i32
+  %2 = trunc i64 %rcx to i32
+  %adc-temp-5369455735- = add i32 %1, %2
+  %realadd-5370894038- = add i32 %adc-temp-5369455735-, %0
+  %stackmemory28430.sroa.2082.1375248.insert.ext = zext i32 %realadd-5370894038- to i64
+  ret i64 %stackmemory28430.sroa.2082.1375248.insert.ext
+}
+
+attributes #0 = { mustprogress nofree norecurse nosync nounwind willreturn memory(none) }
+```
+
+Now, lets see what happens if we choose the other path:
+
+![image](images/branches_1.png)
+```llvm
+; ModuleID = 'my_lifting_module'
+source_filename = "my_lifting_module"
+
+; Function Attrs: mustprogress nofree norecurse nosync nounwind willreturn memory(none)
+define i64 @main(i64 %rax, i64 %rcx, i64 %rdx, i64 %rbx, i64 %rsp, i64 %rbp, i64 %rsi, i64 %rdi, i64 %r8, i64 %r9, i64 %r10, i64 %r11, i64 %r12, i64 %r13, i64 %r14, i64 %r15, ptr nocapture readnone %memory) local_unnamed_addr #0 {
+entry:
+  %stackmemory = alloca i128, i128 13758960, align 8
+  %0 = trunc i64 %r8 to i32
+  %1 = trunc i64 %rdx to i32
+  %2 = trunc i64 %rcx to i32
+  %3 = add i32 %1, %0
+  %realnot-5370192942- = sub i32 %2, %3
+  %stackmemory28817.sroa.3072.1375144.insert.ext = zext i32 %realnot-5370192942- to i64
+  ret i64 %stackmemory28817.sroa.3072.1375144.insert.ext
+}
+
+attributes #0 = { mustprogress nofree norecurse nosync nounwind willreturn memory(none) }
+```
+
+We managed to restore the original logic for branches. Next step would be tying these two paths into one. I do believe using SwitchInst would be more effective for this.
 
 ## Current problems
 
-### Automatically exploring branches and merging two paths into one program
+### Automatically exploring branches and merging multiple paths into one program
 
 ### Some optimization stuff