News for hackers. Stuff that matters.
Re:PartialExecuter: Reducing WebAssembly size by exploring a... by titzer on Tuesday March 15, 2022 @01:33PM (#30688259)
Nice work. I love simple and "conservative brute force" techniques like this--brute force in that you run all the example call sites in the interpreter, conservative in that it bails out when things get hard (e.g. bail out if a single basic block is executed too many times).

I am wondering if this technique could be hybridized with abstract interpretation or partial evaluation, which are known techniques in compilers. In essence, this would become a type of concolic execution.

Re:PartialExecuter: Reducing WebAssembly size by exploring a... by carlopi on Tuesday March 15, 2022 @02:01PM (#30688679)
The step forward that I believe worked well here is that given some actual paths (and since they are simply a sequence of Instruction, they can be fed to an interpreter) they are merged or forked while entering or exiting SCCs, this allows to keep a low count of actual visit but exploring a big enough set of path to prove that it covers all possible executions.

On the second part, I have to do some thinking and coming back, thanks!