Peter Goodman

https://github.com/lifting-bits/anvill/blob/master/tools/decompile-json/tests/specs/ret0.json

Not yet, no. @SaifRushdHadad are you willing to work on this?

Do you have Binary Ninja or IDA Pro? If so, I'd recommend focusing on lifting just with Anvill, as we're underway on a big refactor and it'll help. In the...

So the medium-term plan with McSema is to swap out most of it for Anvill, so that most of the actual lifting is being done by Anvill itself, and McSema...

In the short/medium term not much will change. In the long term we'll probably migrate away from that format, but always strive to have things as a single file. Thus,...

### Making the assembly portable For example: ```asm .align 16 .globl TraceBranch .type TraceBranch, @function TraceBranch: .cfi_startproc ``` A few of these directives might not work on macOS, and we'd...

I see the following error reporting on a missing semantic, which triggers a call to `__remill_sync_hyper_call`, which causes the `State` structure to escape. ``` E0422 16:53:50.833514 93060608 InstructionLifter.cpp:110] Missing semantics...

Use `inst.sub_arch` from inside the function lifter.

Anvill, or parts of anvill, will likely be used in McSema v3, for lifting functions :-) But yes, documentation is needed.

Some thoughts: - `ZExt` and `SExt` return value attributes. We should probably also find a way to put these attributes into `FunctionDecl`s as well. - Investigate downstream uses of the...