Alex Cameron

The SLEIGH build requires quite a modern toolchain: - A C++17 compliant compiler - CMake >= 3.21 Would it be better to skip this benchmark by default and only build...

This is what the benchmark looks like at the moment. I'm planning to profile the benchmark under XRay just to make sure I'm not doing something silly in the benchmark...

> does the decompiler codegen something off of SLEIGH too, making this a representative example of the spec language still? The C++ decompiler portion of GHIDRA can be found [here](https://github.com/NationalSecurityAgency/ghidra/tree/master/Ghidra/Features/Decompiler/src/decompile/cpp)....

From what I can see, the benchmark isn't spending any significant amount of time outside of the Sleigh internals, so I think these results are legit. I've attached a flame...

> The SLEIGH build requires quite a modern toolchain: > > * A C++17 compliant compiler > * CMake >= 3.21 > > Would it be better to skip this...

This is incomplete, I just wanted to ask some questions and check that this approach is looking ok. The example that we looked at that had a `cpuid` instruction is...

I'm trying to figure out what this is doing: https://github.com/lifting-bits/remill/blob/master/cmake/BCCompiler.cmake#L168 It looks like I'll have to add something to here to compile the runtimes for the architecture they're for. At...

Ok, my approach has changed significantly since last time. In order to implement some of these hyper calls (`cpuid` for instance), the only realistic option is to invoke it via...

Seems like I'll need to bring `Limits.h` across too judging from that CI failure. Not sure how it's building fine on my machine. Will look into it more tomorrow. But...

`build_linux` is failing in `master` due to #616. I think this is good to go.