News for hackers. Stuff that matters.

A comment on WebAssembly doesn’t make unsafe languages safe. Parent comment

Re:WebAssembly doesn’t make unsafe languages safe by pcwalton on Sunday November 25, 2018 @04:55PM (#18529304)
ADI doesn't seem to me to have enough bits to effectively protect against vtable type confusion.

Besides, nothing stops a wasm compiler from emitting such checks itself, if it wants to.

[ Parent | on HN ]
Re:WebAssembly doesn’t make unsafe languages safe by pjmlp on Monday November 26, 2018 @12:08AM (#18531210)
Not sure about that, it does seem quite effective, though.

Having the compiler emiting it wouldn't be an option, as hardware enabled solutions seem to be the only ones accepted by C devs, as shown by SPARC and now ARM.

[ Parent | on HN ]
Re:WebAssembly doesn’t make unsafe languages safe by sitkack on Friday November 30, 2018 @08:23PM (#18574362)
I think there is the possibility of integrating the source maps and the WASM with special purpose execution envs to apply these checks.
[ Parent | on HN ]