yarpgen

Oh ok. I have been trying to write emulator and validating if instruction is correctly implemented in my code has been biggest pain point for me as I have no idea to get reference in something like instruction - opcode - context before execution - context after execution. Only thing which I have come up with is just step through the instructions on the MCU using compiled output from yarpgen, but problem here is that it wont generate code variable enough to test all the instructions, so there are going to be blind spots like i.e. float divisions, SIMD instructions etc. https://github.com/intel/yarpgen

One also may bias values to be similar (or equal) to other recently generated values. This was a trick used in the compiler tester yarpgen, where it was useful in testing optimization of bitwise operators on integers. https://github.com/intel/yarpgen https://github.com/intel/yarpgen/blob/main/papers/yarpgen-oo... (see "Policies for constants", page 196:8.)

There are just too many fun things to teach. More recent paper: yarpgen https://github.com/intel/yarpgen/blob/main/papers/yarpgen-oo...

The generator avoids UB, and has found 83 new bugs in GCC, 62 in LLVM, and 76 in the Intel® C++ Compiler. For gcc mostly in the tree-optimizer, sanitizers and x86 backend, but also several wrong rtl-opts and middle-end bugs. With llvm interestingly much more user-visible internal compiler errors (ICE), than silently emitting wrong code as with gcc. https://github.com/intel/yarpgen/

There's also https://github.com/intel/yarpgen which I haven't used. I believe there are a couple of others...