Re:PartialExecuter: Reducing WebAssembly size by exploring a...
by astrange on Wednesday March 16, 2022 @12:31AM
(#30695339)
Seeing through system libraries sounds problematic already, since some of them like libc violate aliasing when you can see their implementations, even in LLVM byte code form.
[ Parent
| on HN ]
Re:PartialExecuter: Reducing WebAssembly size by exploring a...
by carlopi on Thursday March 17, 2022 @05:29AM
(#30709227)
I have to double check this, but the approach should be theoretically sound since we are quite strict with what functions are considered to have known call-sites: Function has to be internal (as in no visibility from outside) + no indirect uses (so no saving a pointer to the function somewhere). This should be enough to solve the problem you are thinking about.
Re:PartialExecuter: Reducing WebAssembly size by exploring a...
by saagarjha on Wednesday March 16, 2022 @06:28AM
(#30697130)
That's actually a good point–more aggressive optimizations that peek through libraries that are not typically visible to the compiler are generally going to break things like allocators. Although, I guess something must be compiling them anyways, so perhaps it might end up OK?