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!
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.